THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Create a new branch named release<YY.MM>
- For example: release18.12 is the name of the release branch created in December, 2018
- Edit the VERSION file in the OFBiz home folder to contain the same <YY.MM> of the release branch
- Modify .github/workflows/codeql-analysis.yml, <<branches: "[ trunk ]">> becomes <<branches: "[ release* ]">>
- In Jira, rename the version "Upcoming Branch" into "<YY.MM.01>" (i.e. the name of the first release of the new branch)
- In Jira, create a new version named "Upcoming Branch" and move to it all the open tasks that were assigned to "Upcoming Branch" and are not planned to be resolved in <YY.MM.01>
- Check Creating a new branch in BuildBot and update the BuildBot.md file
- Update the demos documentation, the next-manual and next patches files under demo-backup
- In the new main README.adoc change from
https://nightlies.apache.org/ofbiz/trunk/readme/html5/[HTML]
https://nightlies.apache.org/ofbiz/trunk/readme/html5/[PDF] format
to
https://nightlies.apache.org/ofbiz/next/readme/html5/[HTML]
or https://nightlies.apache.org/ofbiz/trunk/readme/html5/[PDF] formattrunk to release<YY.MM> where it fits - Update the GitHub workflows files changing from trunk to release<YY.MM> where it fits.
Notably modify .github/workflows/codeql-analysis.yml, <<branches: "[ trunk ]">> to <<branches: "[ release<YY.MM> ]">