Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »


References to ASF official pages

http://www.apache.org/dev/release

http://www.apache.org/dev/release-publishing.html

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

http://www.apache.org/dev/mirrors

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

  1. 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://ci.apache.org/projects/ofbiz/site/stable/rat-output.html. You can include files that don't need license in https://svn.apache.org/repos/asf/ofbiz/tools/rat-excludes.txt
  3. Check no open blocker Jira issues are still pending:
    type key summary assignee reporter priority status resolution created updated due

    JQL and issue key arguments for this macro require at least one Jira application link to be configured


  4. Check if the gradle wrapper version use by this release is present on bintray https://bintray.com/apacheofbiz/GradleWrapper/org.gradle.wrapper. If not the case follow Load new gradle wrapper version on bintray

  5. If you load a new gradle wrapper version, update shasum signature on $OFBIZ_HOME/gradle/init-gradle-wrapper.sh

    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"
  6. Check if there are deprecated services to remove. That's easily done by looking for "has been deprecated and replaced by" in console.log.
  7. Check if there are no licences issues, for that you can use
    https://ci.apache.org/projects/ofbiz/site/stable/rat-output.html for the current stable version
    https://ci.apache.org/projects/ofbiz/site/next/rat-output.html for the current next version, ie the version never released yet

Release Workflow

The workflow for a new release has four phases: preparing a candidate release, voting, publishing the release, announcing the release.

Preparing a Candidate Release

  1. Creates a release tag
  2. Export sthe release branch in a folder named apache-ofbiz-<YY.MM.NN>
  3. Modifies some of the files in the main folder:
    1. 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);
    2. put the release version number in the VERSION file.
  4. Removes the Gradle wrapper bin files
  5. Compresses the exported folder as apache-ofbiz-<YY.MM.NN>.zip
  6. Creates an OpenPGP Compatible ASCII Armored Detached Signature named apache-ofbiz-<YY.MM.NN>.zip.asc
  7. Creates an SHA512 Checksum named apache-ofbiz-<YY.MM.NN>.zip.sha512
  8. Commits the 3 release files to https://dist.apache.org/repos/dist/dev/ofbiz/

Voting on a release

The vote takes place in the developers mailing list. People who want to vote should do the following checks:

  1. check sha checksum of release zip file against the .sha file
  2. check signature of release zip file against the .asc file
  3. unzip the release file, build and run integration tests. The build should be successful.

The checksum and signature verification can also be done by the following convenience script (bash): https://github.com/apache/ofbiz-tools/blob/fdbae25fa8e11355742b403f72cb80f4a0c32262/verify-ofbiz-release.sh

Publishing the Release

After a successful vote, the Candidate Release becomes an official Release and can be published:

  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

http://ofbiz.apache.org/download.html

http://ofbiz.apache.org/source-repositories.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...

Announcing the Release

These steps can be done after at least 24 hours after the release has been published (time required for the propagation of the release files in the mirrors network):

  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
  4. If necessary, update the security page
  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 the release informations on other sites: OFBiz on other sites
  • No labels