feat: change to one release page per version - #297
Merged
Conversation
bsmth
commented
Aug 26, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description:
Proposal from Mkaply to move to a single release page describing all ent-relevant changes per major Fx version.
The main changes here are that we have:
release-notes/firefox.md: this contains a version that will bump every 2 weeks documenting the changes relevant for enterprises, across all release channels, where applicable.Policy additions, deprecations, other changes are documented here.
Motivation:
We're switching to 2-week release cycles and this is an intermediate step to help speed up and automate some of the recurring work.