Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify and document rationale and methodology for release preview versioning #636

Open
Arlodotexe opened this issue Feb 18, 2025 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested

Comments

@Arlodotexe
Copy link
Member

Background

The 8.2 release is ongoing, with tracking of NuGet package releases in #635

Problem

8.2 Preview1 and 8.2 Preview2 have shipped. It's implied that at least one RC needs to ship before Stable, but this is an informed presumption at best and isn't explicitly outlined anywhere.

The rationale behind the versioning methodology for packages published to the public NuGet feed should be clearly documented.

Solution

Investigate and clarify the rationale and methodology for moving between prerelease versions before shipping a stable package.

Once we've gathered this information, we can document it clearly for other maintainers or contributors to reference.

@Arlodotexe Arlodotexe added documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested labels Feb 18, 2025
@Arlodotexe Arlodotexe moved this to 🆕 New in Toolkit 8.x Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants