Skip to content

Suggest changes to beta phase #20280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
seanbudd wants to merge 11 commits into
base: master
Choose a base branch
from
+10 −7
Open

Suggest changes to beta phase #20280

Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
f953576
Suggest changes to beta phase
seanbudd Jun 3, 2026
850cd6d
Suggest changes to beta phase
seanbudd Jun 3, 2026
9186145
Apply suggestion from @seanbudd
seanbudd Jun 3, 2026
60f2c82
Apply suggestions from code review
seanbudd Jun 3, 2026
a65a3bc
drop dead line
seanbudd Jun 3, 2026
2cef285
Merge remote-tracking branch 'refs/remotes/origin/tidyBetaPhase' into…
seanbudd Jun 3, 2026
ef07ac7
Update projectDocs/community/releaseProcess.md
seanbudd Jun 11, 2026
228792c
Update projectDocs/community/releaseProcess.md
seanbudd Jun 11, 2026
e667a3a
Apply suggestion from @seanbudd
seanbudd Jun 15, 2026
b923e64
Update projectDocs/community/releaseProcess.md
seanbudd Jun 16, 2026
f2cb2c4
Apply suggestion from @seanbudd
seanbudd Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions projectDocs/community/releaseProcess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,13 +53,16 @@ Reasons in favor of not reverting the pull request may be:

### Beta phase

* A commit without any known serious issues, will be selected from the 'master' branch and merged into 'beta', this draws the line for features included in the release.
* Documentation changes will be reviewed. A release summary will be added to the change log for the beta.
* A tagged 'beta release' will be created for wider testing.
* New pull requests may be now considered for squash merging straight to beta.
* If addressing regression introduced in this release.
* If addressing a bug in a "must have" feature for this release.
* If addressing a critical Operating System change out of our control.
* A commit will be selected from the `master` branch and merged into `beta`.
* Once a beta commit is chosen, only the following types of changes are included in the release:
* addressing a bug introduced in the current or previous release cycle.
* addressing a `p1` or `p2` filed in the current or previous release cycle.
* reverting code introduced in the current release cycle.
Comment thread
seanbudd marked this conversation as resolved.
* updates to documentation introduced in the current or previous release cycle.
Comment thread
seanbudd marked this conversation as resolved.
* updates to translations.
* Documentation changes will be reviewed.
A release summary will be added to the change log for the beta.
Comment thread
seanbudd marked this conversation as resolved.
* Once considered stable enough, a tagged "beta release" will be created for wider testing.
* As appropriate new tagged beta releases will be published once a week.
* As necessary `beta` will be merged back into master.
* For critical pull requests or translation merges.
Expand Down
Loading