On Mon, Apr 23, 2012 at 11:05 AM, Ralf Gommers <[email protected]>wrote:
> > > On Mon, Apr 23, 2012 at 8:47 AM, Charles R Harris < > [email protected]> wrote: > >> >> >> On Mon, Apr 23, 2012 at 12:22 AM, Ralf Gommers < >> [email protected]> wrote: >> >>> >>> >>> On Sun, Apr 22, 2012 at 3:44 PM, Charles R Harris < >>> [email protected]> wrote: >>> >>>> >>>> On Sun, Apr 22, 2012 at 5:25 AM, Ralf Gommers < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>>>> Aiming for a RC on May 2nd and final release on May 16th would work >>>>>>> for me. >>>>>>> >>>>>>> >>>>>> I count 280 BUG commits since 1.6.1, so we are going to need to thin >>>>>> those out. >>>>>> >>>>> >>>>> Indeed. We can discard all commits related to NA and datetime, and >>>>> then we should find some balance between how important the fixes are and >>>>> how much risk there is that they break something. I agree with the couple >>>>> of backports you've done so far, but I propose to do the rest via PRs. >>>>> >>>> >>> Charles, did you have some practical way in mind to select these >>> commits? We could split it up by time range or by submodules for example. >>> I'd prefer the latter. You would be able to do a better job of the commits >>> touching numpy/core than I. How about you do that one and the polynomial >>> module, and I do the rest? >>> >>> >> I'll give it a shot. I thought the first thing I would try is a search on >> tickets. We'll also need to track things and I haven't thought of a good >> way to do that apart from making a list and checking things off. I don't >> think there was too much polynomial fixing, mostly new stuff, but I'd like >> to use the current documentation. I don't know how you manage that for >> releases. >> > > Nothing too fancy - I use the open tickets for the milestone at > http://projects.scipy.org/numpy/report/3, plus the checklist at > https://github.com/numpy/numpy/blob/master/doc/HOWTO_RELEASE.rst.txt and > perhaps a small todo list in my inbox. Normally we only do bugfix releases > for specific reasons, so besides those I just scan through the list of > commits and pick only some relevant ones of which I'm sure that they won't > give any problems. > > The fixed items under > > http://projects.scipy.org/numpy/query?status=closed&group=resolution&milestone=1.7.0 > > http://projects.scipy.org/numpy/query?status=closed&group=resolution&milestone=2.0.0 > probably give the best overview. > > Argghhh... work ;) But thanks, that's a good starting point... Chuck
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
