Page History
...
Warning | ||
---|---|---|
| ||
You must wait for all the packages to be available at https://search.maven.org/search?q=org.dspace before you announce the release. Until the DSpace packages are available in the Maven repository, no one else will be able to build DSpace using Maven. |
- Add the new contributors to the list: DSpaceContributorsMake sure all contributors to the release have been added to the Release Notes!
- Coordinate Announcements with LYRASIS Staff:
- You might post draft announcements to a service such as https://gist.github.com/ and send out a call to committers for review. When finalized, DSpace releases should be announced on the dspace-community, dspace-devel and dspace-tech lists/groups.
- Announcement on dspace.org, twitter
- (As necessary) 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:
- Current Release
- Next Release Status
- Releases
- NOTE: See DSpace Wiki Style Guide for notes on how to actually edit the above Redirect pages
- Also, update the Documentation Wiki area! Specifically:
- All Documentation page -> Has current release info
- Add a warning to the documentation of the newest unsupported release (e.g. the warning for DSpace 1.7) and link to our Support Policy.
Spaces - Space directory - (i) next to the space - Space Admin - Themes - Configure Theme - Header - Homepage for the current Documentation (e.g. DSpace 6.x Documentation) -> Has links to download latest version of DSpace
- Update the database schema diagram
- For major releases, create a new branch in GitHub for any upcoming bug-fix releases:
- E.g., after the 3.0 release, we created a 3.x branch for any subsequent bug fix releases.
- To automatically create a branch, you may be able to use the release:branch command (NOTE: untested, but it should work! once we test it out, this may be the best practice way of creating a branch).
To manually create a branch, run commands similar to:
Code Block language bash git clone git@github.com:DSpace/DSpace.git branchit cd branchit git checkout -b dspace-3_x dspace-3.0 git push --set-upstream origin dspace-3_x
Then, go back to your
master
checkout, and make sure to update its version numbers in the pom.xml files by running the following:Code Block git checkout master mvn release:update-versions -Dmirage2.on
(Remember to enter in the next appropriate major version number. E.g. After releasing 3.0,
master
should be updated to "4.0-SNAPSHOT", while the new3_x
branch should be at "3.1-SNAPSHOT")- NOTE: the
update-versions
command doesn't always work perfectly. You will want to try a complete rebuild of DSpace before committing anything, as it sometimes misses updating a few version numbers. - Push your verified changes back to GitHub.
- You'll also need to ensure that all version numbers and the
<scm>
section is appropriate in the pom.xml files of your new Branch. Remember, the<scm>
configurations should point at the branch, rather than back atmaster
.
- 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).
- Updates to GitHub:
- Move any uncompleted PRs to the next DSpace version tag / project board
- Close the release milestone (adding date of the release)
- Find the contributors (helpful data for the announcement, you are drafting an announcement, right?):
For bugfix releases
Code Block # This example is to find the list of contributors to 6.3 # It lists contributors to 6.x branch since the 6.2 tag git shortlog -ns dspace-6_x ^dspace-6.2
- For major releases (or from main branch), you can use GitHub contributors pages with a date range.
- Find date of last major release (e.g. 6.0 was released on Oct, 24, 2016)
- Use contributors graph to find contributors between 6.0 and 7.0, e.g. https://github.com/DSpace/DSpace/graphs/contributors?from=2016-10-24&to=2021-07-29&type=c
...