This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 72778016 Update release procedure - automate milestone management
72778016 is described below
commit 7277801639c999589ed9c6a7973eb2f8e04c8d83
Author: Slawomir Jaranowski <[email protected]>
AuthorDate: Mon Nov 24 19:51:29 2025 +0100
Update release procedure - automate milestone management
Milestones are now created and updated automatically during the release
process.
---
.../developers/release/maven-project-release-procedure.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
a/content/markdown/developers/release/maven-project-release-procedure.md
b/content/markdown/developers/release/maven-project-release-procedure.md
index eeaf47e1..efca64ff 100644
--- a/content/markdown/developers/release/maven-project-release-procedure.md
+++ b/content/markdown/developers/release/maven-project-release-procedure.md
@@ -63,11 +63,11 @@ Execute the **Release Drafter** workflow on **GitHub** to
regenerate draft of re
You should **disable** **Release Drafter** workflow on **GitHub** to avoid
adding new items to the release notes after the vote starts and before the
release notes are published. Follow [Disabling and enabling a
workflow](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow)
-## Update milestone in GitHub
+## Check the GitHub milestone
-- close released milestone and open a new one for the next version
-- pull requests merged during votes should be assigned to next milestone
-- Note: For projects which maintain multiple versions, add the branch name
(`branch: branch-name`) to the milestone description.
+- ensure that the milestone version matches the version you are releasing
+- the current milestone will be closed, and a new one for the next version
will be created automatically when you perform the release
+- Note: For projects which maintain multiple versions, add the branch name
(`branch: branch-name`) to the milestone description - all automatically
created milestones will have this branch name in the description
## Make sure that site compilation works
