Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

docs: document new feature stages#16719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
EdwardAngert merged 10 commits intomainfromfeature-stages
Feb 26, 2025
Merged

docs: document new feature stages#16719

EdwardAngert merged 10 commits intomainfromfeature-stages
Feb 26, 2025

Conversation

EdwardAngert
Copy link
Contributor

@EdwardAngertEdwardAngert commentedFeb 26, 2025•
edited
Loading

  • translate notes to docs
  • move to Home > About > Feature Stages
  • decide on bullet point summaries (👍 👎 in comment)

OOS for this PR

add support page that describes how users can get support. currently,this help article is the only thing that pops up and includes thatUsers with valid Coder licenses can submit tickets but doesn't show how, nor does it include the support bundle docs (link or content). it'd be good to have these things relate to each other

preview

preview

@EdwardAngertEdwardAngert added the docsArea: coder.com/docs labelFeb 26, 2025
@EdwardAngertEdwardAngert self-assigned thisFeb 26, 2025
@EdwardAngert
Copy link
ContributorAuthor

how do y'all fee about having a bullet-pointed summary to start each section?

  • Stable: No
  • Production-ready: No
  • Support: GitHub issues
EdwardAngert and bpmct reacted with thumbs up emojiEdwardAngert reacted with thumbs down emoji

Copy link
Member

@bpmctbpmct left a comment•
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Looks great. A couple of thoughts and I know this is early feedback:

  • What do you think about explicitly mentioning which features are in which stage? I don't think this could/should be automated yet (like how we manually change beta labels) but something we should be sure to check before cutting a new release.
  • Thoughts on representing this as a table?
  • LOVE moving it to "About"

@@ -9,37 +9,37 @@ If you encounter an issue with any Coder feature, please submit a

## Early access features

- **Stable**: No
- **Production-ready**: No
- **Support**: GitHub issues
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Can you also mention or "via design partnerships.Contact your account team" or similar. Or do you think this would be implied?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
-**Support**: GitHub issues
-**Support**: GitHub issues or your[Coder account team](https://coder.com/contact)

I'm not familiar with the termdesign partnerships - is it easier if we say something likeFeedback and issues through your [Coder account team](https://coder.com/contact) ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

yeah. i think that's great

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

much better

- **Stable**: No
- **Production-ready**: No
- **Support**: GitHub issues

Early access features are neither feature-complete nor stable. We do not
recommend using early access features in production deployments.

Coder releases early access features behind an “unsafe” experiment, where
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
Coder releases early access features behind an “unsafe” experiment, where
Coderoftenreleases early access features behind an “unsafe” experiment, where

We also sometimes have early access via separate executable which is opt-in, such as the Coder Desktop binary or a module/helm install. So it is not exclusively coupled to experiments

@EdwardAngert
Copy link
ContributorAuthor

EdwardAngert commentedFeb 26, 2025•
edited
Loading

@bpmct

  • What do you think about explicitly mentioning which features are in which stage? I don't think this could/should be automated yet (like how we manually change beta labels) but something we should be sure to check before cutting a new release.

    • That'd be amazing as long as we have triggers in place to keep it updated.

      We haveL45-52 that seems like it's supposed to be built by a script during a release, but I haven't dug into whether or not that's happening/erroringL97 of docs_update_experiments.sh

  • Thoughts on representing this as a table?

    • I don't love how our site deals with wordy tables, but I can try when we've got everything in place so we can see the difference/revert as needed

  • LOVE moving it to "About"

    • ✔️ I'll do this in a later commit so that I don't risk confusing the diff
bpmct reacted with thumbs up emoji

@@ -53,11 +53,31 @@ coder server --experiments=feature1,feature2

## Beta

Beta features are open to the public, but are tagged with a `Beta` label.
- **Stable**: No
- **Production-ready**: Not fully
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
-**Production-ready**:Not fully
-**Production-ready**:Yes. Might not be feature-complete.

bpmct reacted with thumbs up emoji
@EdwardAngertEdwardAngert marked this pull request as ready for reviewFebruary 26, 2025 19:41
Copy link
Member

@bpmctbpmct left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

🚢

Co-authored-by: Ben Potter <ben@coder.com>
@EdwardAngertEdwardAngert merged commit81ef9e9 intomainFeb 26, 2025
29 of 30 checks passed
@EdwardAngertEdwardAngert deleted the feature-stages branchFebruary 26, 2025 20:43
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsFeb 26, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@bpmctbpmctbpmct approved these changes

Assignees

@EdwardAngertEdwardAngert

Labels
docsArea: coder.com/docs
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@EdwardAngert@bpmct
[8]ページ先頭
©2009-2025 Movatter.jp