Skip to content
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.

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

Add steps about milestones and release notes on GitHub to release procedure #682

Merged
merged 1 commit into from
Feb 15, 2025
Merged
Changes from all commits
Commits
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
29 changes: 23 additions & 6 deletions content/apt/developers/release/maven-project-release-procedure.apt
Original file line number Diff line number Diff line change
Expand Up @@ -318,14 +318,31 @@ wagon/wagon-2.2-source-release.zip.sha512

For plugins and shared, you can also run <<<mvn -Pupdate package>>> of the site, then review and commit proposed <<<index.apt>>> updates.

[[3]] Update the version tracking in JIRA
[[3]] Update the version tracking

In the relevant project, go to Administration, then Versions. Mark
the <<<Y.Z>>> version as 'released'. Create version <<<Y.Z+1>>>, if that hasn't already
been done. You may also archive any deprecated releases (milestones or alphas) at this time.
[[a]] Update the version tracking in JIRA

Note: Currently this requires to be in the maven-pmc group. So, if you don't see the Administration option in JIRA, kindly ask <private@maven.apache.org> to do this step for you.
In the relevant project, go to Administration, then Versions. Mark
the <<<Y.Z>>> version as 'released'. Create version <<<Y.Z+1>>>, if that hasn't already
been done. You may also archive any deprecated releases (milestones or alphas) at this time.

Note: Currently this requires to be in the maven-pmc group. So, if you don't see the Administration option in JIRA, kindly ask <private@maven.apache.org> to do this step for you.

[[b]] Update milestone in GitHub

Close released milestone and open new one for next version.

Note: For projects, which maintain multiple versions, add the branch name (<<<branch: branch-name>>>) to the milestone description.

[[c]] Publish release notes draft in GitHub

Check or adapt content to match what you are releasing.

Check version and tag fulfilled in release notes - if not match with published release adjust it.

Note: PR merged after release but before publishing can add next items to release notes draft.

[]

[[4]] Wait for everything to sync

Expand Down Expand Up @@ -373,7 +390,7 @@ https://maven.apache.org/plugins/maven-XXX-plugin/download.cgi

Release Notes - Maven XXX Plugin - Version Y.Z

(Copy Here Release Notes in Text Format from JIRA)
(Copy Here Release Notes in Text Format from JIRA or put a link to GitHub release notes)

Enjoy,

Expand Down