Versions Compared

Old Version 72

changes.mady.by.user Thomas White

Saved on

compared with

New Version 73

changes.mady.by.user Martin Kleppmann

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Check out the branch with:

    No Format
    svn co https://svn.apache.org/repos/asf/avro/branches/branch-X.Y
  2. Update CHANGES.txt to include the release version and date (this change must be committed to trunk and any intermediate branches between trunk and the branch being released).
  3. Update the version number in share/VERSION.txt to be ''avro-X.Y.Z-SNAPSHOT''. Be sure not to leave a trailing newline.

  4. Update the version in the Maven POM files to match with

    No Format
    mvn versions:set -DnewVersion=X.Y.Z-SNAPSHOT -DgenerateBackupPoms=false

  5. Commit these changes.

    No Format
    svn commit -m "Preparing for release X.Y.Z"
  6. Add the fix version X.Y.Z to the Avro JIRA

  7. If not already done, merge desired patches from trunk into the branch and commit these changes. You can find the revision numbers using svn log CHANGES.txt in the branch and in trunk.

    No Format
    cd branch-X.Y
svn merge -rR1:R2 ../trunk .
svn commit -m "Merge -r R1:R2 from trunk to X.Y branch. Fixes: AVRO-A, AVRO-B."
  8. For each patch merged, change the fix version for the JIRA issue to be X.Y.Z
  9. Go through CHANGES.txt, JIRA, and svn log to be sure that the issues included in the branch match in each location, then update the date in CHANGES.txt to be today.
  10. Update the version number in share/VERSION.txt to be ''X.Y.Z''. Be sure not to leave a trailing newline.

  11. Update the version in the Maven POM files to match with

    No Format
    mvn versions:set -DnewVersion=X.Y.Z -DgenerateBackupPoms=false

  12. Update the version number in lang/c/version.sh (the variables libavro_micro_version, libavro_interface_age and libavro_binary_age) according to the libtool versioning rules as described in that file. Note the libtool version number is completely unrelated to the Avro release version number.

  13. Commit these changes.

    No Format
    svn commit -m "Preparing to build X.Y.Z"

  14. Tag the release candidate (R is the release candidate number):

    No Format
    svn copy https://svn.apache.org/repos/asf/avro/branches/branch-X.Y \
https://svn.apache.org/repos/asf/avro/tags/release-X.Y.Z-rcR -m "Avro X.Y.Z-rcR release."

...