Page History
...
| Note | ||
|---|---|---|
| ||
These same steps are also covered in the Sonatype Maven Repository Usage Guide |
The Day Before: Double Check Contents of all README (and similar) files in GitHub
| Info | ||
|---|---|---|
| ||
On skimming these instructions, this might look like a small thing, but it is not. It is a big information management task. Ask for help in wrangling/verifying the license information, and, if at all possible, DO NOT leave this job for release day. |
...
If the file was updated, commit it.
| Anchor | ||||
|---|---|---|---|---|
|
Release DSpace Language Packs (I18N) Modules
Before performing an official release, you should see if the DSpace Language Packs (i18n modules) need an updated release. The easiest way to check if they need to be released it by checking to see if any commits have occurred since the previous release (see below for links). Please note that you can release these I18N Modules on the same day as the main DSpace release. The DSpace parent pom.xml is now configured to also check Sonatype's Release Repository for any Maven artifacts (so you do NOT need to wait for the I18N modules to appear in Maven Central)
...
| Info | ||
|---|---|---|
| ||
Note that the version numbering convention for Language Packs is always the same as the current DSpace release, with an additional |
| Info | ||
|---|---|---|
| ||
Language pack updates are not back-ported. If you are making a security release for an older branch of DSpace, there will be no language pack commits to release. Continue with Final Commits & Preparation, below. |
For each module, perform the full release steps that follow. To save space, the steps are only listed for one of the modules (but don't forget to run it for both language packs):
- Checkout the Language Pack Module:
git clone git@github.com:DSpace/dspace-api-lang.git dspace-api-langcd dspace-api-langgit checkout master
NOTE: always release language packs from the master branch -- we do not use a maintenance branch for language packs.
- Do a Dry Run:
mvn release:prepare -DdryRun=true - 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. 5.0.0, 5.0.1, etc for 5.0 releases of language packs) - NOTE: The release process should suggest the correct version number by default
- Make sure to assign a version number of the format:
- Deploy Artifacts to Staging in Sonatype:
mvn release:perform - Verify and Release Staged Artifacts in Sonatype (see instructions at link)
- Go back and run steps #1-5 above for the other language packs modules (dspace-xmlui-lang)
Once both Language Packs have been released, you can immediately perform the DSpace release. You do not need to wait for them to appear in Maven Central, as our DSpace parent pom.xml will find them in Sonatype's Release Repository immediately.
...
Double Check Language Packs' Version Ranges
...
Overview
Content Tools