Maintainer Guide

Making a Release

  1. Make sure has the right version number
  2. Update NEWS file (use make release-news target and then edit as you see fit)
  3. Run make distcheck, fix any issues and commit.
  4. Upload tarball: scp pygobject-3.X.Y.tar.gz
  5. Install tarball: ssh 'ftpadmin install pygobject-3.X.Y.tar.gz'
  6. Commit NEWS as "release 3.X.Y" and push
  7. Tag with: git tag -s 3.X.Y -m "release 3.X.Y"
  8. Push tag with: git push origin 3.X.Y
  9. Commit post-release version bump to
  10. Send release announcements to;;;
  11. Blog about it (include the HTMLized NEWS that make release-news prints)

Based on


Each cycle after the feature freeze, we create a stable branch so development can continue in the master branch unaffected by the freezes.

  1. Create the branch locally with: git checkout -b pygobject-3-2
  2. Push new branch: git push origin pygobject-3-2
  3. In master, update to what will be the next version number (3.3.0)
  4. Announce the branching, send email telling people to continue development in master and cherry-picking the changes that are appropriate for the stable branch