From f953576451dc683bf96297f6244f3aca22b37f91 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Wed, 3 Jun 2026 17:30:02 +1000 Subject: [PATCH 01/10] Suggest changes to beta phase --- projectDocs/community/releaseProcess.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index b4295e43ae9..2bc721cb58a 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -53,13 +53,15 @@ 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. +* A commit without any known serious issues, will be selected from the 'master' branch and merged into 'beta'. +* Once a beta commit is chosen, no further changes are included in the release, except for: + * addressing a bug introduced in the current or previous release cycle. + * reverting code introduced in the current release cycle. + * addressing a critical Operating System change out of our control. +* 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. * 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. From 850cd6dcf465a3f5a46968f71b9e879cbcc301d8 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Wed, 3 Jun 2026 17:34:58 +1000 Subject: [PATCH 02/10] Suggest changes to beta phase --- projectDocs/community/releaseProcess.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 2bc721cb58a..418f10d5393 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -54,10 +54,10 @@ 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'. -* Once a beta commit is chosen, no further changes are included in the release, except for: +* Once a beta commit is chosen, no further changes are included in the release, except the following will be considered: * addressing a bug introduced in the current or previous release cycle. + * addressing a `p1` filed in the current or previous release cycle. * reverting code introduced in the current release cycle. - * addressing a critical Operating System change out of our control. * 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. From 9186145af9ff61c5825b25b2694fe8b7e895a0f4 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Wed, 3 Jun 2026 17:43:21 +1000 Subject: [PATCH 03/10] Apply suggestion from @seanbudd --- projectDocs/community/releaseProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 418f10d5393..544cb4534e3 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -53,7 +53,7 @@ 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'. +* A commit without any known serious issues, will be selected from the `master` branch and merged into `beta`. * Once a beta commit is chosen, no further changes are included in the release, except the following will be considered: * addressing a bug introduced in the current or previous release cycle. * addressing a `p1` filed in the current or previous release cycle. From 60f2c82e3df0e59b0bb271644dbd1ea5fa055628 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Wed, 3 Jun 2026 17:45:35 +1000 Subject: [PATCH 04/10] Apply suggestions from code review Co-authored-by: Sean Budd --- projectDocs/community/releaseProcess.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 544cb4534e3..ab1e5c07439 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -53,14 +53,14 @@ 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`. +* A commit will be selected from the `master` branch and merged into `beta`. * Once a beta commit is chosen, no further changes are included in the release, except the following will be considered: * addressing a bug introduced in the current or previous release cycle. * addressing a `p1` filed in the current or previous release cycle. * reverting code introduced in the current release cycle. * 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. +* Once considered stable enough, a tagged "beta release" will be created for wider testing. * New pull requests may be now considered for squash merging straight to beta. * As appropriate new tagged beta releases will be published once a week. * As necessary `beta` will be merged back into master. From a65a3bc6d801058dcbc796d1c04662749314e8e1 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Wed, 3 Jun 2026 17:46:34 +1000 Subject: [PATCH 05/10] drop dead line --- projectDocs/community/releaseProcess.md | 1 - 1 file changed, 1 deletion(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 418f10d5393..6a4beb679c4 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -61,7 +61,6 @@ Reasons in favor of not reverting the pull request may be: * 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. * 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. From ef07ac7e74b94b9d25dcaeb71d95287d7f2ec405 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Thu, 11 Jun 2026 10:32:37 +1000 Subject: [PATCH 06/10] Update projectDocs/community/releaseProcess.md Co-authored-by: Sascha Cowley <16543535+SaschaCowley@users.noreply.github.com> --- projectDocs/community/releaseProcess.md | 1 + 1 file changed, 1 insertion(+) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index d3b64642b41..1ddf979653d 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -58,6 +58,7 @@ Reasons in favor of not reverting the pull request may be: * addressing a bug introduced in the current or previous release cycle. * addressing a `p1` filed in the current or previous release cycle. * reverting code introduced in the current release cycle. + * updates to documentation introduced in this release cycle. * Documentation changes will be reviewed. A release summary will be added to the change log for the beta. * Once considered stable enough, a tagged "beta release" will be created for wider testing. From 228792c5933fc937513618e502564fc6f74e1b6d Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Thu, 11 Jun 2026 10:32:53 +1000 Subject: [PATCH 07/10] Update projectDocs/community/releaseProcess.md Co-authored-by: Sascha Cowley <16543535+SaschaCowley@users.noreply.github.com> --- projectDocs/community/releaseProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 1ddf979653d..4db979dc857 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -54,7 +54,7 @@ Reasons in favor of not reverting the pull request may be: ### Beta phase * A commit will be selected from the `master` branch and merged into `beta`. -* Once a beta commit is chosen, no further changes are included in the release, except the following will be considered: +* 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` filed in the current or previous release cycle. * reverting code introduced in the current release cycle. From e667a3af765605a2b74df78199a0e98517d368b5 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Tue, 16 Jun 2026 09:55:40 +1000 Subject: [PATCH 08/10] Apply suggestion from @seanbudd --- projectDocs/community/releaseProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 4db979dc857..26c7de8ac7d 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -56,7 +56,7 @@ Reasons in favor of not reverting the pull request may be: * 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` filed 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. * updates to documentation introduced in this release cycle. * Documentation changes will be reviewed. From b923e64cb63cb8ea940fc02dfd5f9104e8c61528 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Tue, 16 Jun 2026 15:34:37 +1000 Subject: [PATCH 09/10] Update projectDocs/community/releaseProcess.md --- projectDocs/community/releaseProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 26c7de8ac7d..7679a000a4d 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -58,7 +58,7 @@ Reasons in favor of not reverting the pull request may be: * 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. - * updates to documentation introduced in this release cycle. + * updates to documentation introduced in the current or previous release cycle. * Documentation changes will be reviewed. A release summary will be added to the change log for the beta. * Once considered stable enough, a tagged "beta release" will be created for wider testing. From f2cb2c4ccaf35c5fe3d5e1581fa34f4851a4b4b6 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Tue, 16 Jun 2026 15:35:26 +1000 Subject: [PATCH 10/10] Apply suggestion from @seanbudd --- projectDocs/community/releaseProcess.md | 1 + 1 file changed, 1 insertion(+) diff --git a/projectDocs/community/releaseProcess.md b/projectDocs/community/releaseProcess.md index 7679a000a4d..4e4bbeb5d73 100644 --- a/projectDocs/community/releaseProcess.md +++ b/projectDocs/community/releaseProcess.md @@ -59,6 +59,7 @@ Reasons in favor of not reverting the pull request may be: * addressing a `p1` or `p2` filed in the current or previous release cycle. * reverting code introduced in the current release cycle. * updates to documentation introduced in the current or previous release cycle. + * updates to translations. * Documentation changes will be reviewed. A release summary will be added to the change log for the beta. * Once considered stable enough, a tagged "beta release" will be created for wider testing.