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
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
...
...
version of Wiki Documentation is in SVN
Make sure the latest Wiki-based Documentation has been exported as HTML and PDF and committed to [dspace-src]/dspace/docs/ in SVN.
Info | ||
---|---|---|
| ||
See this DSpace documentation management guide: How To Export Downloadable Docs from Wiki |
Note | ||||
---|---|---|---|---|
| ||||
It's often easier to completely remove all current HTML content before committing the updated HTML content. Because of the HTML directory structure exported by Confluence, it can be very difficult to determine which files need removing (especially old attachments). So, you may want to completely remove the old HTML directory, before committing the updated content. An example follows:
|
Double Check Contents of all README (and similar) files in SVN
Make sure that the contents of all README, LICENSE, NOTICE files are up-to-date in SVN. Most of these files exist in one of two main locations:
- [dspace-src]
- includes LICENSE, NOTICE and README files
- [dspace-src]/dspace/
- includes CHANGES, KNOWN_BUGS, LICENSE, NOTICE and README files
Double Check Contents of all README (and similar) files in SVNMake sure that the contents of all README, LICENSE, NOTICE files are up-to-date in SVN. These files reside in [dspace-src. If anything is out-of-date, make sure to update it and commit the proper changes before continuing. Checkout Trunk or Branch to ReleaseCheckout a copy of the to-be-release version either from a branch or trunk.
Do a Dry Run
You will have to enter in your GPG passphrase (which you established when you created your Code Signing Key).
If you notice an issue or an error occurs, you can re-run the Dry Run using the following command:
|
...