NEW-RELEASE (830B)
1 The following steps describe how a new PartKeepr release is being built: 2 3 * Check if any unit tests have failed 4 5 * Edit CHANGELOG.md within the repository 6 7 * Create a new GIT tag using: 8 9 git tag -s <version> 10 11 The tag message should contain a non-verbose list of changes. To view all commits since the last release, use: 12 13 git log <previoustag>..HEAD 14 15 * Push the tag to the repository using: 16 17 git push --tags 18 19 20 * Run the release script on the PartKeepr download server: 21 22 partkeepr-release.sh <tag> 23 24 This generates a release and puts both tbz2 and zip archives into the downloads directory 25 26 27 * Test the archive for errors (simple installation should work) 28 29 * Update the downloads page 30 31 * Create a new version on GitHub 32 33 * Push out notifications on twitter 34 35 * Change irc topic to reflect the current version