This document is aimed at members of the Pony team who might be cutting a release of pony-stable. It serves as a checklist that can take you through doing a release step-by-step.
In order to do a release, you absolutely must have:
- Commit access to the
pony-stablerepo - The latest release of the changelog tool installed
- Access to the ponylang twitter account
- An account on reddit for posting release notes
While not strictly required, you life will be made much easier if you:
- Have a bintray account and have been granted access
pony-languageorganization by a "release admin". - Have read and write access to the ponylang travis-ci account
- Have read and write access to the ponylang appveyor account
Before getting started, you will need a number for the version that you will be releasing as well as an agreed upon "golden commit" that will form the basis of the release. Any commit is eligible to be a "golden commit" so long as:
- It passed all CI checks
We rely on both Travis CI and Appveyor as part of our release process. Both need to be up and functional in order to do a release. Check the status of each before starting a release. If either is reporting issues, push the release back a day or until whenever they both are reporting no problems.
All releases should have a corresponding issue in the pony-stable repo. This issue should be used to communicate the progress of the release (updated as checklist steps are completed). You can also use the issue to notify other pony team members of problems.
Please note that the release script was written with the assumption that you are using a clone of the ponylang/pony-stable repo. It is advised that you use a clone of this repo and not a fork.
For the duration of this document, we will pretend the "golden commit" version is 8a8ee28 and the version is 0.3.1. Any place you see those values, please substitute your own version.
With that in mind, run the release script:
- bash release.bash 0.3.1 8a8ee28
If the golden commit does not include the most recent CHANGELOG updates, you will have to answer n to the second prompt and merge the changes manually.
Leave a comment on the GitHub issue for this release to let everyone know you are done versioning the CHANGELOG and VERSION and that they are updated on master.
By now GitHub should have a listing of this new release under releases. Click the 0.3.1 then do "Edit Release". Paste the CHANGELOG entries for this release into the box and update.
Fork the homebrew-core repo and then clone it locally. You are going to be editing "Formula/pony-stable.rb". If you already have a local copy of homebrew-core, make sure you sync up with the main Homebrew repo otherwise you might change an older version of the formula and end up with merge conflicts.
Make sure you do your changes on a branch:
- git checkout -b pony-stable-0.3.1
HomeBrew has directions on what specifically you need to update in a formula to account for an upgrade. If you are on OSX and are unsure of how to get the SHA of the release .tar.gz, download the release file (make sure it does unzip it) and run shasum -a 256 pony-stable-0.3.1.tar.gz. If you are on OSX, its quite possible it will try to unzip the file on your. In Safari, right clicking and selecting "Download Linked File" will get your the complete .tar.gz.
After updating the pony-stable formula, push to your fork and open a PR against homebrew-core. According to the homebrew team, their preferred naming for such PRs is pony-stable 0.3.1 that is, the name of the formula being updated followed by the new version number.
Leave a comment on the GitHub issue for this release letting everyone know that the Homebrew formula has been updated and a PR issued. Leave a link to your open PR.
During the time since you push to the release branch, Travis CI and Appveyor have been busy building release artifacts. This can take up to a couple hours depending on how busy they are. Periodically check bintray to see if the releases are there yet.
The pattern for releases is similar as what we previously saw. In the case of Deb, the version looks something like:
0.3.1
For windows, the versions look something like:
pony-stable-release-0.3.1-1526.8a8ee28
where the 1526 is the AppVeyor build number and the 8a8ee28 is the abbreviated SHA for the commit we built from.
The Travis CI build for the release branch kicks off packaging builds on Fedora COPR and Ubuntu Launchpad PPA. These packaging builds can take some time but are usually quick. Periodically check to see if the releases are finished and published on these site:
The pattern for packaging release builds is similar as what we previously saw. In the case of Fedora COPR, the version looks something like:
0.3.1-1.fc27
The pattern for packaging release builds is similar as what we previously saw. In the case of Ubuntu Launchpad PPA, the versions looks something like:
pony-stable - 0.3.1-0ppa1~<UBUNTU DISTRIBUTION NAME>
Periodically check on your Homebrew PR. They have a CI process and everything should flow through smoothly. If it doesn't attempt to fix the problem. If you can't fix the problem, leave a comment on the GitHub issue for this release asking for assistance.
Your PR will be closed once your change has been merged to master. Note, that your PR itself will not show as merged in GitHub- just closed. You can use the following command to verify that your change is on Homebrew master:
curl -sL https://raw.githubusercontent.com/Homebrew/homebrew-core/master/Formula/pony-stable.rb | grep urlIf the formulae has been successfully updated, you'll see the new download url in the output of the command. If it hasn't, you'll see the old url.
Note that its often quite quick to get everything through Homebrew's CI and merge process, however its often quite slow as well. We've seen their Jenkins CI often fail with errors that are unrelated to PR in question. Don't wait too long on Homebrew. If it hasn't passed CI and been merged within a couple hours move ahead without it having passed. If Homebrew is being slow about merging, when you inform IRC and pony-user of the release, note that the Homebrew version isn't available yet and include a link to the Homebrew PR and the pony-stable Github release issue so that people can follow along. When the Homebrew PR is eventually merged, update pony-user and IRC.
At this point we are basically waiting on Travis, Appveyor and Homebrew. As each finishes, leave a note on the GitHub issue for this release letting everyone know where we stand status wise. For example: "Release 0.3.1 is now available via Homebrew".
We do a blog post announcing each release. The release notes blog post should include highlights of any particularly interesting changes that we want the community to be aware of.
Additionally, any breaking changes that require end users to change their code should be discussed and examples of how to update their code should be included.
Examples of prior release posts are available. If you haven't written release notes before, you should review prior examples to get a feel what should be included.
To distinguish this pony-stable release from a ponyc release, be sure to title the post: "Pony-stable 0.3.1 Released".
Once all the release steps have been confirmed as successful, merge the PR you created earlier for ponylang.github.io for the blog post announcing the release. Confirm it is successfully published to the blog.
Once Travis, Appveyor and Homebrew are all finished, drop a note in the #ponylang IRC channel (on freenode) letting everyone know that the release is out and include a link the release blog post.
If this is an "emergency release" that is designed to get a high priority bug fix out, be sure to note that everyone is advised to update ASAP. If the high priority bug only affects certain platforms, adjust the "update ASAP" note accordingly.
Once Travis, Appveyor and Homebrew are all finished, send an email to the pony user mailing list letting everyone know that the release is out and include a link the release blog post.
If this is an "emergency release" that is designed to get a high priority bug fix out, be sure to note that everyone is advised to update ASAP. If the high priority bug only affects certain platforms, adjust the "update ASAP" note accordingly.
Last Week in Pony is our weekly newsletter. Add information about the release, including a link to the release notes, to the current Last Week in Pony.
Release notes should be posted to /r/ponylang.
The release should be announced on the ponylang twitter.
Close the GitHub issue for this release.