Page History

...

• Preface - Should contain a very basic overview of the Release. Make sure the Release number is updated here!
  • NOTE: For Subminor 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 History for this latest Release is included. You should be able to just edit the page, copy the fancy code that generated the history for another release, and update the version numbers. For example, copy the previous release's History section and change the release numbers as follows:

  • You'll notice all the release 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+%221.7.0%22 ..." If you look closely, you'll see the 'fixVersion' is set to "1.7.0" in that search string. All you should need to do is update that version number!
  • Also make sure to update the title argument for that jiraissue plugin to list the proper version number information

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

Ensure HTML & PDF versions of Wiki Documentation is in SVN

...