On Tue, Jul 19, 2011 at 6:59 AM, Aaron Meurer <[email protected]> wrote: > By the way, if someone wants to volunteer to handle the release this > time around (or any future time, for that matter), I would be much > obliged. This too would greatly help us do more releases, as it's a > bit of a strain on me to do the release every time. > > It's not too difficult. You just have to follow the guide at > https://github.com/sympy/sympy/wiki/new-release. And I can help you > out if you've never done it before. Let me know if you want to help.
I'd be up for helping you, but I'll have internet access only up to Friday so we'd have to finish before that. I'm not sure if I could handle doing it all, but I'll gladly help with the packaging and stuff. Also, the wiki page contains references to the test_pure_* scripts which I've removed in one of the commits in your "remove-2.4-cruft" pull - I didn't know they were used. I wanted to update the wiki page, but maybe it's better if you do it. > > Aaron Meurer > > On Sat, Jul 16, 2011 at 5:13 PM, Aaron Meurer <[email protected]> wrote: >> I have already asked some of you on the respective pull requests, but >> help with the release notes would be appreciated, especially for those >> of you who contributed significant changes (like the GSoC students). >> They are at https://github.com/sympy/sympy/wiki/Release-Notes-for-0.7.1. >> I am going through now and doing all the smaller changes, and I will >> ask the respective people for help with the larger ones, but any kind >> of help from anyone is appreciated. >> >> Aaron Meurer >> >> On Sat, Jul 16, 2011 at 10:57 AM, Aaron Meurer <[email protected]> wrote: >>> Hi everyone. >>> >>> As some of you may know, we've just fixed isympy to work with the new >>> IPython 0.11, which will be released in about a week. Therefore, I'd >>> like to do a SymPy 0.7.1 release in about a week or so, so that people >>> can update to the new version of IPython (which is awesome btw). >>> >>> I'd like to so this fairly soon, so most of the existing stuff that >>> isn't in will be postponed until the next release. I won't be able to >>> start any kind of release cycle until Monday, so you can push stuff in >>> until then. I'd like to get my branch putting MathJax in the docs in, >>> if it's possible, so we can push it out to everyone and best see if >>> it's a good idea. >>> >>> But please don't feel bad if your stuff is postponed, even if it's >>> currently in a pull request (your best bet is to solicit reviews >>> within the next few days). As I've said before, I'd like to release >>> more often, and I think the key to doing this is to try to get a >>> faster release cycle. Our dev branch is generally quite stable, so >>> this should be possible in theory. I'd also be interested in hearing >>> any ideas on ways to get a faster release cycle from people with >>> experience in this area. >>> >>> By the way, I haven't run the tests in master in a while. Is >>> everything passing? >>> >>> Aaron Meurer >>> >> > > -- > 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. > > -- Vladimir Perić -- 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.
