Releasing a new CKAN client

Myk edited this page Oct 27, 2017 · 12 revisions

When merging pull requests

Merging pull requests is a great time to update You can do this as a separate commit on master, but with a bit of git-fu you can update it as part of the merge commit itself!

$ git checkout master
$ git merge someuser/somebranch --no-commit --no-ff # This merges your PR, but doesn't commit it.
$ vim                                  # Or whatever your favourite editor is, if not vim.
$ git add
$ git commit -m 'Merge #<PR-Num> <Description>'     # This commits the merge, *and* your changes to
$ git push

This has the advantage that if the merge is undone, so is the changelog entry.

Making sure the changelog is up-to-date is important for our next step, which is...

Before the release

  1. Build the final code base and test that CKAN will launch on both Windows and Linux, will install, remove and update mods.
  2. Ideally, create a Pre-release first and ask the @MacOS-Testers and @Wranglers teams to try the new client and report any issues.

Making a release!

CKAN releases are mostly automated, but the full process is:

  1. Go to draft a new release, fill in the version (don't forget the leading v; eg v1.2.3), and title (which is a cool release name of your choosing).
  2. We traditionally have a release picture that relates to the title. The textbox at the bottom lets you upload a picture. While it looks funny, you can use the standard [title](url) markdown syntax to make a link, except instead of a title you have a the image reference (![](url...)). If you're unsure, look at the text of a previous release to see what it looks like.
  3. Have a line of three dashes (---) by themselves, with a blank line on either side, after the release image. The updater program expects to see this, so it doesn't include the image in the text-only release notes.
  4. Copy'n'paste in the release notes for this version, usually from the changelog. Add extra notes if necessary.
  5. Add another line of three dashes, and provide attribution for the release image. Again, the updater program expects to see this.
  6. Hit the release button and celebrate!

You do not need to build the binary. Travis will see the new tag, build a binary, run it through tests, and upload the assets when complete. Once they're uploaded, the client updater will show a new release is available to users and ask if they wish to upgrade.

After the release

  1. Update the IRC channel topic with the version of the new release.
  2. Update the forum thread topic with the version and date of the new release.
  3. Post in the forum with release notes and a link to the releases page.
  4. Start a new "unreleased" stub in the changelog file.
  5. Congratulate yourself on a job well done!

Improvements that can be made to the release process

Right now the release project requires a human to copy'n'paste in a changelog, which is silly, because that could be done by a bot. In the future the ideal release process would simply be choosing a release name and image, and having bots do the rest.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.