Skip to content

re-write release guide #3707

Closed
Closed

Description

@tacaswell

current one is a tad out of date. This is a brain dump of what I have done for the last 3 releases. Here instead of a PR as I didn't plan to type out the list when I created the issue.

  • make sure all of the testing and such is done (pretty easy now that we have travis)
  • run github stats script to update the contributor and issue logs
  • bump version to release target and commit
  • create (and optionally sign) tag
  • create doc branch off of the new tag
  • version bump back to dev version and commit
  • merge everything back to master
  • checkout tag
  • push tag and updated branches to github
  • turn tag into a Release
  • run git clean -xfd to make sure stray files don't make it into the dist
  • run python setup.py sdist to make clean source tarball
  • kick off building the mac wheels (https://travis-ci.org/MacPython/matplotlib-wheels)
  • create folders on SF (matplotlib-X.Y.Z + windows, mac sub-folders)
  • upload tarball to SF
  • email windows builder
  • email linux/conda/canopy maintainers
  • run python setup.py sdist upload --sign to upload to pypi (this assumes .pypirc is set up)
  • collect wheels + exe for windows and mac and upload to pypi (use twine) + SF
  • upload all the binaries to pypi
  • get a DOI from https://zenodo.org/
  • manually update citing.html with DOI link in doc/_templates
  • install the tagged version
  • build the docs and copy to new folder (X.Y.Z) matplotlib.github.com repo
  • copy new files to top level folder
  • manually update downloads.txt + rerun update_downloads.py
  • manually update versions.html
  • commit all changes to matplotlib.github.com master and push upstream
  • announce to all three mailing lists + g+ + twitter

Activity

  1. self-assigned this
    on Oct 23, 2014
  2. added this to the v1.4.3 milestone on Oct 23, 2014
  3. mdboom commented on Oct 23, 2014

    @mdboom
    Member

    This is a real testament to all the hard work you've been doing, and a good thing to link to next time someone asks why the release is delayed :)

    This is one of those things that would be nice to automate, but is very hard to automate. Any rethinking or streamlining along those lines would be great, of course -- maybe it would be helpful to have someone on one of the other large scipy-community projects to look at this and offer advice. There always seem to be little tricks in this space that are hard to find.

  4. modified the milestones: v1.4.x, v1.4.3 on Dec 30, 2014
  5. modified the milestones: , v1.4.x on Feb 7, 2015
  6. modified the milestones: , on Aug 14, 2015
  7. modified the milestones: , on Oct 26, 2015
  8. 6 remaining items

  9. removed this from the milestone on Oct 30, 2015
  10. modified the milestones: , on Dec 28, 2015
  11. modified the milestones: , on Mar 28, 2016
  12. modified the milestones: , on May 3, 2017
  13. tacaswell commented on Oct 8, 2017

    @tacaswell
    MemberAuthor

    Thas was done in #7635

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions