Hi, On Mon, Jul 18, 2016 at 4:56 PM, Robert Bradshaw <rober...@gmail.com> wrote: > On Fri, Jul 15, 2016 at 4:22 AM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> Hi, >> >> On Fri, Jul 15, 2016 at 9:32 AM, Stefan Behnel <stefan...@behnel.de> wrote: >>> Hi all! >>> >>> I just pushed a bug-fix-only release for the current 0.24 series. >>> The update should be safe for everyone using 0.24. >>> >>> https://pypi.python.org/pypi/Cython/0.24.1 >>> >>> Complete changelog follows below. >>> >>> SHA1 sum: >>> a837efb73c195585ce6e27cf53e3587285ccd39f Cython-0.24.1.tar.gz >> >> Thanks a lot for the release. >> >> I'm just building wheels via >> https://travis-ci.org/MacPython/cython-wheels - will upload soon. It >> would be good to get the wheels up before the source archive, if at >> all possible, to make sure that users don't get a blip where they >> don't have wheels for a while. Building should be straightforward, >> just a new commit to https://github.com/MacPython/cython-wheels with >> an edit to give the new tag name. If y'all agree that's a good idea, >> what's the best way to update the release procedure? > > Good point. > > I'm not sure the best process (for wheels on all platforms)--maybe an > email before we push to pypi once we've settled on what commit to > release? (Typically we have a thread of release candidates, etc.)
Yes, that would certainly help. If whoever is releasing, wants to do the wheel building, the procedure is here: https://github.com/MacPython/cython-wheels#triggering-a-build (summary, edit appveyor and travis files to set tag, commit and push). But, if you shoot me an email, I'm happy to do it too, Cheers, Matthew _______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel