slawekjaranowski commented on code in PR #682: URL: https://github.com/apache/maven-site/pull/682#discussion_r1955104189
########## content/apt/developers/release/maven-project-release-procedure.apt: ########## @@ -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 <priv...@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 <priv...@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 project with maintain multiple current version add branch name in milestone description: <<<branch: branch-name>>> Review Comment: text will be enough - screenshots can extend page length.... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
