Page History

...

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

1. heck Check if there are any bugfixes in trunk which need to be backported to the release branch (see How should committers handle backporting?).
2. Check all files are correctly licensed at https://cinightlies.apache.org/projects/ofbiz/site/stable/rat-output.html. For that you can use
   https://cinightlies.apache.org/projects/ofbiz/site/stable/rat-output.html for the current stable version
   https://cinightlies.apache.org/projects/ofbiz/site/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
3. Check no open blocker Jira issues are still pending:

   Jira
   server ASF JIRA jqlQuery filter=12344205 serverId 5aa69414-a9e9-3523-82ec-879b028fb15b

4. 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"

   
   

5. Check if there are deprecated services to remove. That's easily done by looking for "has been deprecated and replaced by" in console.log.
6. Update the developers page on site: https://ofbiz.apache.org/developers.html

...

1. move the release files from https://dist.apache.org/repos/dist/dev/ofbiz/ to https://dist.apache.org/repos/dist/release/ofbiz/

Updating related files

...

1. /

...

1. ofbiz

...

1. /

...

https://github.com/apache/ofbiz-tools/blob/master/demo-backup/README.md

https://github.com/apache/ofbiz-site/blob/master/doap_OFBiz.rdf

Please complete the list if necessary...

Announcing the Release

These steps can be done after at least 15 minutes after the release has been published (time required for the transmission of the release files to the CDN):

1. Add a news item to the main page of the OFBiz website: http://ofbiz.apache.org/index.html
2. Add the information about the release to the OFBiz download page: http://ofbiz.apache.org/download.html
3. Create an html page with the release notes (generated by Jira)
   
   1. In Jira, mark the version as "released" and create a new version for the next release
4. If necessary, update the security page on siote
5. Add the information about the release to the release history page: http://www.apache.org/dist/ofbiz/
6. Send an announcement to the user, dev and announce@apache.org lists; if the release contains vulnerability fixes send also to security@apache.org

7. Update related files

   http://ofbiz.apache.org/download.html
   http://ofbiz.apache.org/source-repositories.html
   http://ofbiz.apache.org/security.html
   https://github.com/apache/ofbiz-tools/blob/master/demo-backup/README.md
   https://github.com/apache/ofbiz-site/blob/master/doap_OFBiz.rdf
   Please complete the list if necessary...

8. Update the release informations on other sites: OFBiz on other sites
9. If it's an EOL release announce using one of the files at https://svn.apache.org/repos/private/pmc/ofbiz/security/EOL-Drafts

Creating a new release branch

...