About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
changelog:release_checklist

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
changelog:release_checklist [2016/08/02 13:28] demiankatzchangelog:release_checklist [2021/09/20 10:59] (current) demiankatz
Line 3: Line 3:
 Follow these steps to make a new VuFind release.  (This page is primarily for Demian's reference). Follow these steps to make a new VuFind release.  (This page is primarily for Demian's reference).
  
 +  * Make sure full test suite is passing in both MySQL and PostgreSQL configurations.
 +  * Make sure that [[installation:vagrant|Vagrant]] configuration still works.
   * Make sure packages/DEBIAN/control, packages/DEBIAN/changelog contain correct version numbers and dates for new release.   * Make sure packages/DEBIAN/control, packages/DEBIAN/changelog contain correct version numbers and dates for new release.
-  * Make sure build.xml and (if applicable) pom.xml or package.json reflect correct version number.+  * Make sure build.xml and package.json reflect correct version number. Remember that package.json version number must have three parts -- e.g. 3.1.0, not 3.1.
   * Make sure config.ini generator setting reflects correct version number.   * Make sure config.ini generator setting reflects correct version number.
-  * Tag a new release in Git or Subversion.+  * Tag a new release in Git.
   * Tag the corresponding browse handler version in [[https://github.com/vufind-org/vufind-browse-handler|GitHub]].   * Tag the corresponding browse handler version in [[https://github.com/vufind-org/vufind-browse-handler|GitHub]].
   * Check out the tagged release.   * Check out the tagged release.
Line 13: Line 15:
   * Test/update [[installation:migration_notes|migration notes]].   * Test/update [[installation:migration_notes|migration notes]].
   * Upload packages to Sourceforge; be sure to set new default download.   * Upload packages to Sourceforge; be sure to set new default download.
 +  * Upload binaries to the GitHub release and include link to changelog in description.
   * Test/update [[:installation|installation notes]] for all platforms.   * Test/update [[:installation|installation notes]] for all platforms.
   * Update [[http://vufind.org/downloads.php|Downloads]] page and the news footer in GitHub pages to point to new release.   * Update [[http://vufind.org/downloads.php|Downloads]] page and the news footer in GitHub pages to point to new release.
   * Update release status in [[http://vufind.org/jira|JIRA]].   * Update release status in [[http://vufind.org/jira|JIRA]].
 +  * Close [[https://github.com/vufind-org/vufind/milestones|milestone]] on GitHub.
   * Post news article on Sourceforge feed.   * Post news article on Sourceforge feed.
-  * Post announcements to mailing lists: vufind-general, vufind-tech, code4lib, web4lib, ngc4lib +  * Post announcements to mailing lists: vufind-general, vufind-tech, code4lib, web4lib 
-  * Send press release to [[http://www.librarytechnology.org|Marshall Breeding]] and [[http://www.advancedtechnologylibraries.com/|Advanced Technology/Libraries]] (judyduke AT optonline DOT net). +  * Send press release to [[https://librarytechnology.org|Marshall Breeding]] and Rachel Fadlon.
-  * Create release entry on [[http://foss4lib.org/|foss4lib.org]].+
   * Tweet release on [[https://twitter.com/vufindorg|@vufindorg]].   * Tweet release on [[https://twitter.com/vufindorg|@vufindorg]].
   * Update the live demo to the new version.   * Update the live demo to the new version.
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
changelog/release_checklist.1470144483.txt.gz · Last modified: 2016/08/02 13:28 by demiankatz