Versions Compared

Old Version 12

changes.mady.by.user Malin Nicolas

Saved on

compared with

New Version 13

changes.mady.by.user Malin Nicolas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add "update shasum for new gradle version"

...

  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/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 that no open blocker Jira issues are still pending:
    Jira
    serverASF JIRA
    jqlQueryfilter=12344205
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b

  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

    Code Block
    languagebash
    titleSHASUM 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"


Release Workflow

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

...