chore: add milestone section on the contribution page #1923
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
innocenzi
reviewed
Jan 26, 2026
|
|
||
| Tempest current does not follow a fixed release cycle. In general, bug fixes and minor features can be released as soon as possible. For breaking changes, though, we aim to bundle as many as possible in a single major release. | ||
|
|
||
| ### Milestones |
Member
There was a problem hiding this comment.
I struggle with seeing "2.x" or "3.x" as a milestone. For me it's supposed to be a goal to reach, not something you track continuously.
I would suggest we use specific milestones for minor versions. eg. milestone 3.4 should contain the specific fixes and features assigned for its milestone.
That way, we have a very specific goal to work towards.
If we don't like that, I'd suggest leaving out the concept of "current minor milestone" entirely, and just work on stuff as we see fit and occasionally release patches and minors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.