Replies: 2 comments
-
For clarity: I am arguing that all products under the ProjectReunion umbrella are NOT forced to have the same version number. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Good question Matt, we're working on finalizing and documenting this, all of our questions are very valuable and we'll ensure that we capture all of these! We'll post an update here when we have final versions. Thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As Project Reunion will encompass multiple products, it will help developers working with those products if they all adopt the same standards and conventions for version numbering and how early releases are handled. This will avoid confusion and prevent developers making incorrect assumptions about those products.
Clearly documenting these (as part of the ProjectReunion docs) will also serve as a useful reference for both consumers and creators of products that are part of ProjectReunion.
As developers we want to spend time working with the products, not trying to remember or looking up the differences.
Version numbers
Will version numbers of the product be tied to the version number of ProjectReunion releases?
Does version 1.x imply a stable, supported release?
How will version numbers be incremented?
Will all projects follow semver conventions? (I know this covers above points but I wanted to call them our specifically)
Early releases
Please define terms (including but not limited to) "alpha", "beta", "preview", "pre-release", "stable", "go-live", "supported", "GA", "go to market"
Please ensure that pre-release labels applied to packages use the same conventions.
Beta Was this translation helpful? Give feedback.
All reactions