This is an automated email from the ASF dual-hosted git repository. sejer pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/incubator-wayang-website.git
The following commit(s) were added to refs/heads/main by this push: new 8b8198d3 Update how-to-make-a-release.md 8b8198d3 is described below commit 8b8198d3c922239b8812ad943862c0f5f35154c3 Author: mspruc <55182629+msp...@users.noreply.github.com> AuthorDate: Tue Jun 24 10:12:39 2025 +0200 Update how-to-make-a-release.md fix numbering --- docs/community/how-to-make-a-release.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/community/how-to-make-a-release.md b/docs/community/how-to-make-a-release.md index 94e36e33..8dc5680f 100644 --- a/docs/community/how-to-make-a-release.md +++ b/docs/community/how-to-make-a-release.md @@ -24,23 +24,23 @@ Please note that `mvn:release` commands eagerly commit directly to your working - ``mvn release:branch -DbranchName=rel/1.0.0-rc5`` -4. Switch to branch: +3. Switch to branch: ``git checkout rel/1.0.0-rc5`` -5. Set upstream of branch: +4. Set upstream of branch: ``git push -u <remote_name> <branch_name>`` -6. Update RELEASE_NOTES and check NOTICE to have the correct year +5. Update RELEASE_NOTES and check NOTICE to have the correct year -7. Check if everything is working: +6. Check if everything is working: ``mvn clean install`` -8. Check if there are no SNAPSHOT references: ``find . -type f -name 'pom.xml' -exec grep -l "SNAPSHOT" {} \;`` +7. Check if there are no SNAPSHOT references: ``find . -type f -name 'pom.xml' -exec grep -l "SNAPSHOT" {} \;`` -9. Run ``mvn release:clean`` +8. Run ``mvn release:clean`` -10. Modify the tag in the root pom.xml file to contain the right version with the rc number: +9. Modify the tag in the root pom.xml file to contain the right version with the rc number: `` <tag>v1.0.0-rc5</tag>`` (2 places in the file) Now depending if it's the first time you do a release continue with the following steps, otherwise jump to step **16**.