servoshell: Prepare November release (0.0.3) #40962
Merged
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
Member
|
Maybe it makes sense to actually release another micro release rather than immediately jumping to 0.1? The API is still in flux and I suspect we won't get to a stable place until early next year. |
Member
Author
|
Note this just bumps servoshell, not |
Prepare for the next release by cutting a version on the last day of the month. There are still ongoing discussion on defining what 1.0 means, but there was a consensus, that we could use 0.x versioning to explore what semantic versioning could look like in servo. Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
mrobinson
approved these changes
Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As discussed in the tsc-channel, prepare for the next release by cutting a version on the last day of the month.
Note: The actual release would happen ~ 2 weeks from now, when the blog post for november is ready.
This commit was produced by running
./mach release 0.0.3.Testing: Not required. Additional pre-release testing will happen after the version bump and before the release, with potential patches being cherry-picked to a release branch.