Page History
...
If everything looks good, select the repository and select "Release". The artifacts should be synced to central within an hour, and will officially be released to http://repo2.maven.org/maven2/org/dspace/
Create the Distribution Zips for SourceForge
The previous action will have checked out the release tag into the target directory under "target/checkout". Navigate to that directory and execute the creation of the distributions using the following command. This will create two zip, bzip and gzipped files in the target directory. One set of files is the "binary" release, and the other set is the source release.
(Note: If you've already removed the target/checkout directory, you can also checkout a fresh copy of the newly tagged version and run this command from the DSpace parent directory.)
| Code Block |
|---|
localhost$ cd target/checkout
localhost$ mvn package -Pdistributions
[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building DSpace Parent Project
[INFO] task-segment: [package]
[INFO] ----------------------------------------------------------------------------
[INFO] [site:attach-descriptor]
[INFO] [assembly:single -(execution. default-)]
[INFO] Building zip: .../target/dspace-1.5.0-beta1-release.zip
[INFO] Building tar: .../target/dspace-1.5.0-beta1-release.tar.gz
[INFO] Building tar: .../target/dspace-1.5.0-beta1-release.tar.bz2
[INFO] Building zip: .../target/dspace-1.5.0-beta1-src-release.zip
[INFO] Building tar: .../target/dspace-1.5.0-beta1-src-release.tar.gz
[INFO] Building tar: .../target/dspace-1.5.0-beta1-src-release.tar.bz2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
|
Upload to SourceForge
Upload both the source and binary releases to Sourceforge.net. You can either upload them via the web interface, or copy them over via scp or other command line tools. If you want to copy the files from command line, follow the directions found here:
http://apps.sourceforge.net/trac/sourceforge/wiki/File%20management%20service
Using scp to copy to the "DSpace Stable" file directory: (example for 1.6.0 final)
| Code Block |
|---|
scp <files> <username>,dspace@frs.sourceforge.net:"/home/frs/project/d/ds/dspace/DSpace\\ Stable/1.6.0/"
|
Using scp to copy to the "DSpace Release Candidate" file directory: (example for 1.6.0-rc2)
| Code Block |
|---|
scp <files> <username>,dspace@frs.sourceforge.net:"/home/frs/project/d/ds/dspace/DSpace\\ Release\\ Candidate/1.6.0-rc2/"
|
WARNING: You must wait for all the packages to be available at http://repo2.maven.org/maven2/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.
After the Release is Finished
- Add the new contributors to the list: DSpaceContributors
- Coordinate Announcements with DuraSpace Staff:
- Announcement on dspace.org, duraspace.org, twitter
- Plus if new stable version, ask dspace.org admins to upload latest documentation
- Announce on mailing lists
- Link announcement on Home of Wiki, change any version numbers on that page.
- Ensure that the Latest Release page on dspace.org is updated.
- Add group corresponding to the version to the JIRA system (if not already there)
- Update Wiki pages, particularly these pages which refer to the Current and Next releases:
- Create a new branch in SVN for any upcoming sub-minor releases (if necessary)
Overview
Content Tools