THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Check if there are any bugfixes in trunk which need to be backported to the release branch (see How should committers handle backporting?).
- Check all files are correctly licensed at https://nightlies.apache.org/ofbiz/stable/rat-output.html. For that you can use
https://nightlies.apache.org/ofbiz/stable/rat-output.html for the current stable version
https://nightlies.apache.org/ofbiz/next/rat-output.html for the current next version, ie the version never released yet
You can include files that don't need license in https://github.com/apache/ofbiz-tools/blob/master/rat-excludes.txt - Check no open blocker Jira issues are still pending:
Jira server ASF JIRA jqlQuery filter=12344205 serverId 5aa69414-a9e9-3523-82ec-879b028fb15b If you load a new gradle wrapper version, update shasum signature on $OFBIZ_HOME/gradle/init-gradle-wrapper.sh
Code Block language bash title SHASUM GRADLE # checksum to verify the downloaded file SHASUM_GRADLE_WRAPPER_FILES="1d23286bcb9e7d3debff18c1b892b9dbb9a4ec6c gradle/wrapper/gradle-wrapper.jar f9c2ad227ef1fe774cb0e141abfc431b05fc9fd4 gradle/wrapper/gradle-wrapper.properties b4a6a7e1dca81a692a775193fada937e035265f3 gradlew"
- Check if there are deprecated services to remove. That's easily done by looking for "has been deprecated and replaced by" in console.log.
- Update the developers page on site: https://ofbiz.apache.org/developers.html
Release Workflow
The workflow for a new release has four phases: preparing a candidate release, voting, publishing the release, announcing the release.
...
- Create a release tag named: release<YY.MM.NN>
- For example: release18.12.02
- Create the release tag on all the relevant repositories such as ofbiz-framework and ofbiz-plugins
- Export/extract the release branch in a local folder named apache-ofbiz-<YY.MM.NN>
- Modify the following files in the main folder:
- edit the LICENSE file: if it is a framework+plugins release then simply remove the LICENSE file under plugins; if it is a framework only release then edit the LICENSE file to remove the references to plugins; if it is a plugin release that add NOTICE and check the validity of the LICENSE file (or add one if missing);
- put the release version number in the VERSION file.
- Remove the Gradle wrapper bin files
- Compress the exported folder as apache-ofbiz-<YY.MM.NN>.zip
- Create an OpenPGP Compatible ASCII Armored Detached Signature named apache-ofbiz-<YY.MM.NN>.zip.asc
- Create an SHA512 Checksum named apache-ofbiz-<YY.MM.NN>.zip.sha512
- Commit the 3 release files to https://dist.apache.org/repos/dist/dev/ofbiz/
- Change Update the release number on Site developers page and developers page on site: https://ofbiz.apache.org/developers.html and the doap_OFBiz.rdf file
Voting on a release
...