And there is a problem with building the docs, which should be fixed. I would do it like it says https://github.com/sympy/sympy/wiki/new-release. Create a new branch 0.7.2 in the official repo. Then, all release blocking PRs should go as pull requests to that branch. Development on master can continue as usual. Also, I was thinking that you should create a pull request to merge 0.7.2 into master right away, so that we can run the bot tests on it (but don't merge it until the release is finished).
I'll help out too. Basically everything that you need to do is on that wiki page. Just let me know what you plan to do yourself, and what you want me to do. The hardest part at this point is actually the stuff at the bottom, after you've released, because there are a dozen websites and packages to update, so any help there is the most appreciated. Also, go through the 0.7.2 blocker issues and make sure that either they are fixed or can be reasonably postponed. Aaron Meurer On Sun, Aug 5, 2012 at 1:34 PM, Tom Bachmann <[email protected]> wrote: > I think there may be some 3.3 problems with hash randomization still. For > example 1462. Also, when running use2to3, there is a problem in some > docstring, which I think 1463 is trying to address. > > Probably aaron and smichr know more. > > > On 05.08.2012 20:26, Ondřej Čertík wrote: >> >> Hi, >> >> Tests seem to be working in master in Travis: >> >> http://travis-ci.org/#!/sympy/sympy/builds >> >> as well as my computer. What has to be done to make the release? >> Are there any PR's that should go in? >> >> Unless there is somebody else interested, I will go ahead with this >> release. >> It should be 0.7.2, right? Here is my plan: >> >> * I'll release rc1 >> * we'll have source tarball, win32.exe, the documentation >> * I'll follow (possibly update) the >> https://github.com/sympy/sympy/wiki/New-Release >> * from the source tarball, one can run the bin/use2to3 script to get >> Python 3.x support, >> but it takes a long time. So I plan to also release python 3.x source >> tarball and python 3.x >> win32.exe. >> >> That way people that want to have one source tarball for all Python's >> will just use the regular >> tarball (that can do python 2.x immediately and then they need to run >> a script to get 3.x support). >> People that just want 3.x support can just grab the 3.x tarball (or >> .exe on windows). >> >> Ondrej >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
