Page History

...

Using scp to copy to the "DSpace Stable" file directory: (example for 1.83.0 final)
(NOTE: You will need to first create the 'DSpace Stable/1.83.0' directory via SourceForge's Admin UI)

scp <files> <username>,dspace@frs.sourceforge.net:"/home/frs/project/d/ds/dspace/DSpace\\ Stable/13.8.0/"

Using scp -r to copy to the "DSpace Release Candidate" file directory: (example for 1.83.0-rc2rc1)
(NOTE: You will need to first create a folder in your target directory, named "1.83.0-rc2rc1" or whatever the name of the release is, and then mv all the tar.gz and zip files to that folder... you're going to recursively scp the entire contents of that folder to Sourceforge)

...

• 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:
  
  • Current Release
  • Next Release Status
  • RoadMap
  • 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
  • Homepage for the current Documentation (e.g. DSpace 14.8 x Documentation) -> Has links to download latest version of DSpace
• 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

    (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 new 3_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 at master.
• For major releases, after you create the maintenance branch (see above), DuraSpace Bamboo should automatically notice the new branch and add it to our existing Bamboo build plan.
  • NOTE: Bamboo assumes the branch name will start with "dspace-"
  • You may want to jump over to DuraSpace Bamboo to ensure that the branch now appears under our main project: https://bamboo.duraspace.org/browse/DST-TRUNK/branches
• 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).

...