All, * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0 (w/o support to Python 2.3) ? I need to correct an elusive bug in numpy.ma.MaskedArray and wondered whether I needed to backport it or not (1.1.x would likely be affected as well). Thanks a lot in advance, P.
On Mon, Aug 4, 2008 at 9:49 AM, Pierre GM <pgmdevlist@gmail.com> wrote:
* What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0 (w/o support to Python 2.3) ?
There are currently no plans for 1.1.2. Not that it won't happen; it's just that there hasn't been any plans for the release. And I very much doubt there will be any serious discussion of releasing 1.1.2 before 1.2.0. Here is the current 1.2.0 schedule: - 8/08/08 tag the 1.2.0rc1 release and prepare packages - 8/15/08 tag the 1.2.0rc2 release and prepare packages - 8/23/08 tag the 1.2.0 release and prepare packages - 8/24/08 announce release I moved the rc dates forward a bit since I didn't get 1.1.1 out as early as I had hoped, which means I haven't had time to look over the current state of the trunk. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/
On Mon, Aug 4, 2008 at 10:10 AM, Jarrod Millman <millman@berkeley.edu> wrote:
Here is the current 1.2.0 schedule:
- 8/08/08 tag the 1.2.0rc1 release and prepare packages - 8/15/08 tag the 1.2.0rc2 release and prepare packages - 8/23/08 tag the 1.2.0 release and prepare packages - 8/24/08 announce release
I was just talking to Robert and he pointed out that we should have a beta release first. So I am renaming 1.2.0rc1 to 1.2.0b1 and 1.2.0rc2 is now 1.2.0rc1. The plan is still to try and get 1.2.0 out on 8/24. Just to be clear the schedule is: - 8/08/08 tag the 1.2.0b1 release and prepare packages - 8/15/08 tag the 1.2.0rc1 release and prepare packages - 8/23/08 tag the 1.2.0 release and prepare packages - 8/24/08 announce release -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/
HI Pierre, On Mon, Aug 4, 2008 at 11:49 AM, Pierre GM <pgmdevlist@gmail.com> wrote:
All, * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0 (w/o support to Python 2.3) ? I need to correct an elusive bug in numpy.ma.MaskedArray and wondered whether I needed to backport it or not (1.1.x would likely be affected as well). Thanks a lot in advance, P.
I don't know what the schedule is, but if you have a bug fix it is probably a good idea to back port it to 1.1.x so that any future release will be easier. Also, if you do do the backport, put an informative comment with the commit. Chuck
On Mon, Aug 4, 2008 at 10:17 AM, Charles R Harris <charlesr.harris@gmail.com> wrote:
I don't know what the schedule is, but if you have a bug fix it is probably a good idea to back port it to 1.1.x so that any future release will be easier. Also, if you do do the backport, put an informative comment with the commit.
I agree with the caveat that your focus should be mostly on 1.2 at this point. If your fix for 1.2 is not easy to back port to 1.1.x, I wouldn't worry about it too much. Ideally we will get all the fixes in 1.2 back to 1.1.x, but it isn't absolutely essential that every fix make it back. That said I would really like to see as many fixes as possible applied to both the trunk and the last stable release branch. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/
Charles, Jarrod, That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in 1.1.x, so I just commited the changes to the 2 versions. I was just wondering for how long I would have to backport this kind of fixes.
I agree with the caveat that your focus should be mostly on 1.2 at this point. If your fix for 1.2 is not easy to back port to 1.1.x, I wouldn't worry about it too much. Ideally we will get all the fixes in 1.2 back to 1.1.x, but it isn't absolutely essential that every fix make it back. That said I would really like to see as many fixes as possible applied to both the trunk and the last stable release branch.
Thanks,
On Mon, Aug 4, 2008 at 1:07 PM, Pierre GM <pgmdevlist@gmail.com> wrote:
Charles, Jarrod, That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in 1.1.x, so I just commited the changes to the 2 versions. I was just wondering for how long I would have to backport this kind of fixes.
I agree with the caveat that your focus should be mostly on 1.2 at this point. If your fix for 1.2 is not easy to back port to 1.1.x, I wouldn't worry about it too much. Ideally we will get all the fixes in 1.2 back to 1.1.x, but it isn't absolutely essential that every fix make it back. That said I would really like to see as many fixes as possible applied to both the trunk and the last stable release branch.
I think one more 1.1.x release might be appropriate, if only to have one solid version out for Python 2.3. Hopefully Scipy will also release a compatible version. And then we should put an end date on the series, say Jan 1, 2009 or maybe after the first bugfix release of 1.2. Chuck
On Mon, Aug 4, 2008 at 13:40, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Mon, Aug 4, 2008 at 1:07 PM, Pierre GM <pgmdevlist@gmail.com> wrote:
Charles, Jarrod, That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in 1.1.x, so I just commited the changes to the 2 versions. I was just wondering for how long I would have to backport this kind of fixes.
I agree with the caveat that your focus should be mostly on 1.2 at this point. If your fix for 1.2 is not easy to back port to 1.1.x, I wouldn't worry about it too much. Ideally we will get all the fixes in 1.2 back to 1.1.x, but it isn't absolutely essential that every fix make it back. That said I would really like to see as many fixes as possible applied to both the trunk and the last stable release branch.
I think one more 1.1.x release might be appropriate, if only to have one solid version out for Python 2.3. Hopefully Scipy will also release a compatible version.
Too late for that. SVN scipy already requires SVN numpy. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Mon, Aug 4, 2008 at 12:31 PM, Jarrod Millman <millman@berkeley.edu>wrote:
I don't know what the schedule is, but if you have a bug fix it is
a good idea to back port it to 1.1.x so that any future release will be easier. Also, if you do do the backport, put an informative comment with
On Mon, Aug 4, 2008 at 10:17 AM, Charles R Harris <charlesr.harris@gmail.com> wrote: probably the
commit.
I agree with the caveat that your focus should be mostly on 1.2 at this point. If your fix for 1.2 is not easy to back port to 1.1.x, I wouldn't worry about it too much. Ideally we will get all the fixes in 1.2 back to 1.1.x, but it isn't absolutely essential that every fix make it back. That said I would really like to see as many fixes as possible applied to both the trunk and the last stable release branch.
Thanks,
-- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
participants (4)
-
Charles R Harris -
Jarrod Millman -
Pierre GM -
Robert Kern