-
Notifications
You must be signed in to change notification settings - Fork 690
Publishing a maintenance release
Gregory Brown edited this page Jan 6, 2014
·
37 revisions
- Verify that the code in the
stablebranch is what you actually want to release. - Run the tests on the stable branch. Make sure you can get a passing local build.
- Check the latest Travis CI builds for the stable branch and make sure they match the current latest commit, and are green across all supported Rubies.
- Build the manual and do a quick visual skim of its contents to make sure it's working properly.
- If any new documentation was added to the manual in this release, upload a new version of the manual to the github pages website. (TODO: explain this in more detail)
- Copy relevant notes from MasterCHANGELOG to CHANGELOG.
- Make sure CHANGELOG is fully up to date. Verify by looking at git history, even if it looks right.
- Prepare a blog post for elmcitycraftworks.org (we'll later move these announcements to prawnpdf.org)
- Announce on prawn-ruby mailing list and on Twitter.