CommunityToolkit / CommunityToolkit/Windows

Clarify and document rationale and methodology for release preview versioning

Open
#636 0 comments 0 reactions 2 assignees Claimed by @michael-hawker View on GitHub
documentation enhancement question
Dominant language
C#
Stars
1.1k
Forks
166
PR merge metrics
No merged PRs in 30d

Description

# Background

The 8.2 release is ongoing, with tracking of NuGet package releases in https://github.com/CommunityToolkit/Windows/issues/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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.