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.
• Tag a new release in Subversion.
• 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 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 build.xml and pom.xml in trunk to reflect next expected version number.
• Update the live demo to the new version.