Page History

...

• If you'd like to release a Snapshot Release of that module, follow the instructions at: Making a Snapshot Release (e.g. 'dspace-x.y-SNAPSHOT')
• If you'd like to tag & release a new version of that module, use the module instructions at: Release Procedure#Release DSpace Language Packs (I18N) Modules (NOTE: These instructions obviously have some specific notes around how the Language Packs modules are versioned. You obviously don't need to follow those versioning notes. Individual modules may have their own version schemes)

...

1. Checkout the Language Pack Module:
   
   1. git clone git@github.com:DSpace/dspace-api-lang.git dspace-api-lang

   2. cd dspace-api-lang
   3. git checkout master
2. Release Procedure#Do Do a Dry Run: mvn release:prepare -DdryRun=true
3. Release Procedure#Tag Tag and Increment Version: mvn release:prepare -Dresume=false
   
   • Make sure to assign a version number of the format: [major].[minor].[sequence-number] (e.g. 3.0.0, 3.0.1, etc for 3.0 releases of language packs)
   • NOTE: The release process should suggest the correct version number by default
4. Release Procedure#Deploy Deploy Artifacts to Staging in Sonatype: mvn release:perform
5. Release Procedure#Verify Verify and Release Staged Artifacts in Sonatype (see instructions at link)
6. Go back and run steps #1-5 above for the other language packs modules (dspace-xmlui-lang)

...

• Add the new contributors to the list: DSpaceContributors
• Coordinate Announcements with DuraSpace Staff:
  
  • Announcement on dspace.org, duraspace.org, twitter
  • Ensure that the Latest Releasepage 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 1.8 Documentation) -> Has links to download latest version of DSpace
• For major releases, create a new branch in GitHub for any upcoming bug-fix releases: (NOTE: BRANCH INSTRUCTIONS NEED UPDATE FOR GITHUB!)
  
  • E.g., after 1the 3.8.0 release, we created a 13.8.x branch for the subsequent 1.8.1 and 1.8.2 releasesany 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 a command commands similar to:

    Code Block
    language bash
    git clone git@github.com:DSpace/DSpace.git branchit cd branchit git checkout -b dspacesvn copy http://scm.dspace.org/svn/repo/dspace/trunk \ http://scm.dspace.org/svn/repo/dspace/branches/dspace-3_x \dspace-3.0 git push --set-upstream origin -m "Creating a branch for 3.x bug-fix releases."dspace-3_x

     

    • Then, go back to your Trunk checkout, and make sure to update its version numbers in the pom.xml files by running the following:

      Code Block
      mvn release:update-versions

      (Remember to enter in the next appropriate major version number. E.g. After releasing 3.0, Trunk 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.
    • 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 Trunk.
• For major releases, make sure to create a new DuraSpace BambooProject to auto-build the new branch you created in GitHub.
  
  • Usually, it's easiest to just 'clone' the existing Trunk project, rather than starting from scratch.
  • You'll want to name it something similar to "18BRANCH" (for 1.8.x branch).
• 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).

...