
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