Warning: This page has not been updated in over over a year and may be outdated or deprecated.
changelog:release_checklist
This is an old revision of the document!
Release Checklist
Follow these steps to make a new VuFind release. (This page is primarily for Demian's reference).
- Make sure packages/DEBIAN/control and packages/DEBIAN/changelog contain correct version numbers and dates for new release.
- Make sure build.xml and (if applicable) pom.xml reflect correct version number.
- Make sure config.ini generator setting reflects correct version number.
- Tag a new release in Git or Subversion.
- Tag the corresponding browse handler version in GitHub.
- Check out the tagged release.
- Run “phing package” to build packages.
- Update changelog.
- Test/update migration_notes.
- Upload packages to Sourceforge; be sure to set new default download.
- Test/update installation notes for all platforms.
- Update Downloads page and the news footer in GitHub pages to point to new release.
- Update release status in JIRA.
- Post news article on Sourceforge feed.
- Post announcements to mailing lists: vufind-general, vufind-tech, code4lib, web4lib, ngc4lib
- Send press release to Marshall Breeding and Advanced Technology/Libraries (judyduke AT optonline DOT net).
- Create release entry on foss4lib.org.
- Update the live demo to the new version.
changelog/release_checklist.1450112821.txt.gz · Last modified: 2015/12/14 17:07 by demiankatz