Versions Compared

Old Version 95

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 96

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added 'mvn install' instructions & cleanup of the notes about answering release questions

...

Checkout Master or Branch to Release

Checkout a fresh copy of the to-be-release version either from a branch or master. For example:

Code Block
git clone git@github.com:DSpace/DSpace.git ~/dspace-release
git checkout master

Update your Local Maven Cache

Before starting the release, you should ensure your local maven cache (~/.m2/repository) is completely up-to-date by running:

Code Block
mvn install

Updating your local maven cache will help to ensure that the release process goes more smoothly, and should help you to avoid any errors having to do with Maven being unable to locate any particular dependencies.

Do a Dry Run

This step is not required, but performs a useful sanity check without committing any changes. From your clean, up-to-date copy of master/branch, run the following command (from [dspace-src]):

...

The above command will ask you three basic questions. Here are sample answers for DSpace 3.0:

Panel

"What is the release version for: XXX" : 3.0

  • NOTE: This is the release # to put in the final tagged Maven POMs. E.g. for
  • Examples:
    • For a "3.0" final release, it should look like: 3.0
    • For a "3.0 Release Candidate #1" release, it
    would
    • should look like:
    "
    • 3.0-rc1
    "

"What is SCM release tag or label for: XXXX" : dspace-3.0

  • NOTE: This is the tag name in GitHub.  E.g. for . 
  • Examples:
    • For a "3.0" final release, it should look like: dspace-3.0
    • For a "3.0 Release Candidate #1" release, it
    would
    • should look like:
    "
    • dspace-3.0-rc1
    ")

"What is the new development version for: XXXX" : 3.1-SNAPSHOT

  • NOTE: This is the next release number which all POMs should be incremented to on "master"branch. E.g. .
  • Examples:
    • For a "3.0" final release (3.0), the next version should be: 3.1-SNAPSHOT
    • For a "3.0
    for
    • Release Candidate #1
    , it would look like: "
    • " release (3.0-rc1), the next version should be: 3.0-rc2-SNAPSHOT
    "

You will also have to enter in your GPG passphrase (which you established when you created your Code Signing Key).

...