Page History
...
- Add the new contributors to the list: DSpaceContributors
- Coordinate Announcements with DuraSpace Staff:
- Announcement on dspace.org, duraspace.org, twitter
- Ensure that the Latest Release page on dspace.org is updated.
- Plus, ask dspace.org admins to upload latest documentation in PDF/HTML format
- Announce on all DSpace mailing lists
- Link announcement on Home of DSpace Wiki, change any version numbers listed on that page.
- Update Wiki pages, particularly these pages which refer to the Current and Next Releases:
- CurrentRelease
- Next Release Status
- RoadMap
- NOTE: See DSpace Wiki Style Guide for notes on how to actually edit the above Redirect pages
- For major releases, create a new branch in SVN for any upcoming sub-minor releases:
- E.g., after 1.6.0 release, we created a 1.67.x branch for the subsequent 1.6.1 and 1.6.2 releases
- To create a branch, run a command similar to:
Code Block svn copy http://scm.dspace.org/svn/repo/dspace/trunk \ http://scm.dspace.org/svn/repo/dspace/branches/dspace-1_6_x \ -m "Creating a branch for 1.6.x bug-fix releases."
- Then, go back to your Trunk checkout, and make sure to update it's version numbers in the pom.xml files by running the following:
(Remember to enter in the next appropriate major version number. E.g. After releasing 1.6.0, Trunk should be updated to "1.7.0-SNAPSHOT", while the new 1_6_x branch should be at "1.6.1-SNAPSHOT")Code Block mvn release:update-versions
- Updates to JIRA:
- Move any uncompleted issues to the next DSpace version tag in JIRA.
- Ask a JIRA Administrator to close out the release in JIRA (this will ensure no new issues can be added to that release).
...
Overview
Content Tools