Page History

References to ASF official pages

...

https://www.apache.org/dev/release-signing.html

http://www.apache.org/dev/mirrors (deprecated, historically interesting)

Things to check before a release (these tasks can be delegated by the RM (Release Manager))

...

1. Create a new branch named release<YY.MM>
   1. For example: release18.12 is the name of the release branch created in December, 2018
2. Edit the VERSION file in the OFBiz home folder to contain the same <YY.MM> of the release branch
3. In Jira, rename the version "Upcoming Branch" into "<YY.MM.01>" (i.e. the name of the first release of the new branch)
4. 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>
5. Check Creating a new branch in BuildBot and update the BuildBot.md file
   
6. Update the demos documentation, the next-manual and next patches files under demo-backup
   
7. In the new main README.adoc change from trunk to  release<YY.MM> where it fits
8. 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> ]">

Branch EOL (End Of Life)

In order to help our users to decide about what to do with branches EOL we decide x months ago to send an announcement. When the time is passed we send a confirmation announcement about the EOL.

For now we have only sent a direct announcement (no pre-announcement) for 17.12.09 release. A draft for the 18.12 branch exists. These are only accessible to PMC members.