Versions Compared

Old Version 224

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 225

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  • Release Notes- Should contain a very basic overview of the Release. Make sure the Release number is updated here!
    • NOTE: For minor releases (bug-fix-only releases), you may want to leave all information about the previous major release, and just enhance the content to state that this was a bug-fix release, and list any new contributors, etc.
  • Installation - Obviously make sure the Installation Documentation is updated for this Release
  • Upgrading a DSpace Installation - Same for the Upgrade Documentation, make sure it's up to date

  • History- Make sure the online History for this latest Release is included.

    You should be able to just copy the last version's page and update the version numbers. For example, copy the previous release's page, and change as follows:
  • You'll notice all the JIRA history is generated via the jiraissue plugin. In the url argument for that plugin, you should find the DSpace version number embedded in the querystring like: "... AND+fixVersion+%3D+%223.0%22 ..." If you look closely, you'll see the 'fixVersion' is set to "3.0" in that search string. All you should need to do is update that version number (and the plugin will now search for tickets closed for 4.0)
    • Also make sure to update the title argument for that jiraissue plugin to list the proper version number information

    This section just links to all the tickets/PRs closed under the release "milestone" in GitHub.

    Note

    Obviously, this is just a brief reminder of important areas of Documentation which always require updates. There's surely other areas, like Configuration section, which will require some updates for your release.


Ensure you tag multiple releases in chronological order!

...