headers
Robert Bradshaw | 1 May 21:07
Favicon

Re: [Cython] 0.11.2 release schedule?

On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:

> Dag Sverre Seljebotn wrote:
>> Like I've been saying on some occasions, I'm going show off Cython  
>> 18th
>> of May, and have had a tendency to scratch some itches rather than
>> planning how to explain them... so I'd really like a release to  
>> happen
>> before then. (Though I also have some fixes/rewrites which are not  
>> done
>> yet which will go in next week.)
>>
>> If it helps I can play release manager this time and do the  
>> groundwork
>> for making it build Sage etc. (especially if that gets us complex  
>> floats
>> in time :-)).
>>
>> Would it be possible to e.g. do a full stop feature freeze next  
>> Friday
>> 8th, and then a release the week after?
>
> I'm not currently working on cython-devel anyway, so I'm glad to  
> hear that
> you volunteer as QA manager. :)

Yes, that would be great if you would do the release managing-- 
definitely would make a mid-May release more feasible.

> There are tons of open issues assigned to 0.11.2, though. I don't
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 1 May 22:00
Picon
Picon

Re: [Cython] 0.11.2 release schedule?

Robert Bradshaw wrote:
> On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:
> 
>> Dag Sverre Seljebotn wrote:
>>> Like I've been saying on some occasions, I'm going show off Cython  
>>> 18th
>>> of May, and have had a tendency to scratch some itches rather than
>>> planning how to explain them... so I'd really like a release to  
>>> happen
>>> before then. (Though I also have some fixes/rewrites which are not  
>>> done
>>> yet which will go in next week.)
>>>
>>> If it helps I can play release manager this time and do the  
>>> groundwork
>>> for making it build Sage etc. (especially if that gets us complex  
>>> floats
>>> in time :-)).
>>>
>>> Would it be possible to e.g. do a full stop feature freeze next  
>>> Friday
>>> 8th, and then a release the week after?
>> I'm not currently working on cython-devel anyway, so I'm glad to  
>> hear that
>> you volunteer as QA manager. :)
> 
> Yes, that would be great if you would do the release managing-- 
> definitely would make a mid-May release more feasible.

I'll give it a try.
(Continue reading)

Permalink | Reply |
headers
Robert Bradshaw | 12 May 20:12
Favicon

Re: [Cython] 0.11.2 release schedule?

On May 1, 2009, at 1:00 PM, Dag Sverre Seljebotn wrote:

> Robert Bradshaw wrote:
>> On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:
>>
>>> Dag Sverre Seljebotn wrote:
>>>> Like I've been saying on some occasions, I'm going show off Cython
>>>> 18th
>>>> of May, and have had a tendency to scratch some itches rather than
>>>> planning how to explain them... so I'd really like a release to
>>>> happen
>>>> before then. (Though I also have some fixes/rewrites which are not
>>>> done
>>>> yet which will go in next week.)
>>>>
>>>> If it helps I can play release manager this time and do the
>>>> groundwork
>>>> for making it build Sage etc. (especially if that gets us complex
>>>> floats
>>>> in time :-)).
>>>>
>>>> Would it be possible to e.g. do a full stop feature freeze next
>>>> Friday
>>>> 8th, and then a release the week after?
>>> I'm not currently working on cython-devel anyway, so I'm glad to
>>> hear that
>>> you volunteer as QA manager. :)
>>
>> Yes, that would be great if you would do the release managing--
>> definitely would make a mid-May release more feasible.
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 12 May 20:20
Picon
Picon

Re: [Cython] 0.11.2 release schedule?

Robert Bradshaw wrote:
> On May 1, 2009, at 1:00 PM, Dag Sverre Seljebotn wrote:
> 
>> Robert Bradshaw wrote:
>>> On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:
>>>
>>>> Dag Sverre Seljebotn wrote:
>>>>> Like I've been saying on some occasions, I'm going show off Cython
>>>>> 18th
>>>>> of May, and have had a tendency to scratch some itches rather than
>>>>> planning how to explain them... so I'd really like a release to
>>>>> happen
>>>>> before then. (Though I also have some fixes/rewrites which are not
>>>>> done
>>>>> yet which will go in next week.)
>>>>>
>>>>> If it helps I can play release manager this time and do the
>>>>> groundwork
>>>>> for making it build Sage etc. (especially if that gets us complex
>>>>> floats
>>>>> in time :-)).
>>>>>
>>>>> Would it be possible to e.g. do a full stop feature freeze next
>>>>> Friday
>>>>> 8th, and then a release the week after?
>>>> I'm not currently working on cython-devel anyway, so I'm glad to
>>>> hear that
>>>> you volunteer as QA manager. :)
>>> Yes, that would be great if you would do the release managing--
>>> definitely would make a mid-May release more feasible.
(Continue reading)

Permalink | Reply |
headers
Stefan Behnel | 12 May 20:52
Picon
Favicon

Re: [Cython] 0.11.2 release schedule?


Dag Sverre Seljebotn wrote:
> Robert Bradshaw wrote:
>> Dag, any chance on a beta in the near future? Finishing up complex  
>> support is #2 on my todo list, so it'll get pushed today.
> 
> Yes, sorry, I got sidetracked for a few days (and left the tree in a 
> defect state over the weekend as a bonus...). But I'm doing "make check" 
> on Sage as I write this and things are looking good.
> 
> I was planning on doing it in a few hours, though if you're pushing 
> complex support soon I might wait until after then.

Just a quick note that lxml builds and tests nicely with cython-devel on
Py2.5 and 3.1. So a beta is ok over here.

Stefan
Permalink | Reply |
headers
Robert Bradshaw | 12 May 20:34
Favicon

Re: [Cython] 0.11.2 release schedule?

On May 12, 2009, at 11:20 AM, Dag Sverre Seljebotn wrote:

> Robert Bradshaw wrote:
>> On May 1, 2009, at 1:00 PM, Dag Sverre Seljebotn wrote:
>>
>>> Robert Bradshaw wrote:
>>>> On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:
>>>>
>>>>> Dag Sverre Seljebotn wrote:
>>>>>> Like I've been saying on some occasions, I'm going show off  
>>>>>> Cython
>>>>>> 18th
>>>>>> of May, and have had a tendency to scratch some itches rather  
>>>>>> than
>>>>>> planning how to explain them... so I'd really like a release to
>>>>>> happen
>>>>>> before then. (Though I also have some fixes/rewrites which are  
>>>>>> not
>>>>>> done
>>>>>> yet which will go in next week.)
>>>>>>
>>>>>> If it helps I can play release manager this time and do the
>>>>>> groundwork
>>>>>> for making it build Sage etc. (especially if that gets us complex
>>>>>> floats
>>>>>> in time :-)).
>>>>>>
>>>>>> Would it be possible to e.g. do a full stop feature freeze next
>>>>>> Friday
>>>>>> 8th, and then a release the week after?
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 12 May 21:53
Picon
Picon

Re: [Cython] 0.11.2 release schedule?

Robert Bradshaw wrote:
> On May 12, 2009, at 11:20 AM, Dag Sverre Seljebotn wrote:
> 
>> Robert Bradshaw wrote:
>>> On May 1, 2009, at 1:00 PM, Dag Sverre Seljebotn wrote:
>>>
>>>> Robert Bradshaw wrote:
>>>>> On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:
>>>>>
>>>>>> Dag Sverre Seljebotn wrote:
>>>>>>> Like I've been saying on some occasions, I'm going show off  
>>>>>>> Cython
>>>>>>> 18th
>>>>>>> of May, and have had a tendency to scratch some itches rather  
>>>>>>> than
>>>>>>> planning how to explain them... so I'd really like a release to
>>>>>>> happen
>>>>>>> before then. (Though I also have some fixes/rewrites which are  
>>>>>>> not
>>>>>>> done
>>>>>>> yet which will go in next week.)
>>>>>>>
>>>>>>> If it helps I can play release manager this time and do the
>>>>>>> groundwork
>>>>>>> for making it build Sage etc. (especially if that gets us complex
>>>>>>> floats
>>>>>>> in time :-)).
>>>>>>>
>>>>>>> Would it be possible to e.g. do a full stop feature freeze next
>>>>>>> Friday
(Continue reading)

Permalink | Reply |
headers
Michael Abshoff | 12 May 22:04

Re: [Cython] 0.11.2 release schedule?

Dag Sverre Seljebotn wrote:
> Robert Bradshaw wrote:

<SNIP>

Hi Dag,

> Status on Sage is that these fail:
> 
>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>          sage -t  "devel/sage/sage/rings/integer.pyx"
>          sage -t  "devel/sage/sage/plot/plot.py"
>          sage -t  "devel/sage/sage/interfaces/maxima.py"
> 
> The last two seem to be because of fragile doctests. 

Can you post the first doctest failure from each failing file?

Cheers,

Michael
Permalink | Reply |
headers
Dag Sverre Seljebotn | 12 May 22:21
Picon
Picon

Re: [Cython] 0.11.2 release schedule?

Michael Abshoff wrote:
> Dag Sverre Seljebotn wrote:
>> Robert Bradshaw wrote:
> 
> <SNIP>
> 
> Hi Dag,
> 
>> Status on Sage is that these fail:
>>
>>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>>          sage -t  "devel/sage/sage/rings/integer.pyx"
>>          sage -t  "devel/sage/sage/plot/plot.py"
>>          sage -t  "devel/sage/sage/interfaces/maxima.py"
>>
>> The last two seem to be because of fragile doctests. 
> 
> Can you post the first doctest failure from each failing file?

This is on Sage 3.4.1 (my own build).

sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
**********************************************************************
File 
"/home/dagss/sage/sage-3.4.1/devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx", 
line 751:
     sage: f.leading_coefficient()
Exception raised:
     Traceback (most recent call last):
       File "/home/dagss/sage/sage-3.4.1/local/bin/ncadoctest.py", line
(Continue reading)

Permalink | Reply |
headers
Michael Abshoff | 12 May 22:30

Re: [Cython] 0.11.2 release schedule?

Dag Sverre Seljebotn wrote:
> Michael Abshoff wrote:
>> Dag Sverre Seljebotn wrote:
>>> Robert Bradshaw wrote:
>> <SNIP>
>>
>> Hi Dag,
>>
>>> Status on Sage is that these fail:
>>>
>>>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>>>          sage -t  "devel/sage/sage/rings/integer.pyx"
>>>          sage -t  "devel/sage/sage/plot/plot.py"
>>>          sage -t  "devel/sage/sage/interfaces/maxima.py"
>>>
>>> The last two seem to be because of fragile doctests. 
>> Can you post the first doctest failure from each failing file?
> 
> This is on Sage 3.4.1 (my own build).

Ok. Which compiler and host? 3.4.2 is out by the way and 4.0.alpha0 
should drop tonight :)

> sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
> **********************************************************************

<SNIP>

>      OverflowError: can't convert negative value to unsigned int
> **********************************************************************
(Continue reading)

Permalink | Reply |
headers
Robert Bradshaw | 12 May 22:54
Favicon

Re: [Cython] 0.11.2 release schedule?

On May 12, 2009, at 1:30 PM, Michael Abshoff wrote:

> Dag Sverre Seljebotn wrote:
>> Michael Abshoff wrote:
>>> Dag Sverre Seljebotn wrote:
>>>> Robert Bradshaw wrote:
>>> <SNIP>
>>>
>>> Hi Dag,
>>>
>>>> Status on Sage is that these fail:
>>>>
>>>>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>>>>          sage -t  "devel/sage/sage/rings/integer.pyx"
>>>>          sage -t  "devel/sage/sage/plot/plot.py"
>>>>          sage -t  "devel/sage/sage/interfaces/maxima.py"
>>>>
>>>> The last two seem to be because of fragile doctests.
>>> Can you post the first doctest failure from each failing file?
>>
>> This is on Sage 3.4.1 (my own build).
>
> Ok. Which compiler and host? 3.4.2 is out by the way and 4.0.alpha0
> should drop tonight :)
>
>
>> sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>> ********************************************************************* 
>> *
>
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 12 May 22:40
Picon
Picon

Re: [Cython] 0.11.2 release schedule?

Michael Abshoff wrote:
> Dag Sverre Seljebotn wrote:
>> Michael Abshoff wrote:
>>> Dag Sverre Seljebotn wrote:
>>>> Robert Bradshaw wrote:
>>> <SNIP>
>>>
>>> Hi Dag,
>>>
>>>> Status on Sage is that these fail:
>>>>
>>>>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>>>>          sage -t  "devel/sage/sage/rings/integer.pyx"
>>>>          sage -t  "devel/sage/sage/plot/plot.py"
>>>>          sage -t  "devel/sage/sage/interfaces/maxima.py"
>>>>
>>>> The last two seem to be because of fragile doctests. 
>>> Can you post the first doctest failure from each failing file?
>> This is on Sage 3.4.1 (my own build).
> 
> Ok. Which compiler and host? 3.4.2 is out by the way and 4.0.alpha0 
> should drop tonight :)

dagss <at> boksen:~/sage/sage-3.4.1$ uname -a
Linux boksen 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 
x86_64 GNU/Linux

dagss <at> boksen:~/sage/sage-3.4.1$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
(Continue reading)

Permalink | Reply |
headers
Michael Abshoff | 12 May 22:45

Re: [Cython] 0.11.2 release schedule?

Dag Sverre Seljebotn wrote:
> Michael Abshoff wrote:
>> Dag Sverre Seljebotn wrote:
>>> Michael Abshoff wrote:
>>>> Dag Sverre Seljebotn wrote:
>>>>> Robert Bradshaw wrote:
>>>> <SNIP>
>>>>
>>>> Hi Dag,
>>>>
>>>>> Status on Sage is that these fail:
>>>>>
>>>>>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>>>>>          sage -t  "devel/sage/sage/rings/integer.pyx"
>>>>>          sage -t  "devel/sage/sage/plot/plot.py"
>>>>>          sage -t  "devel/sage/sage/interfaces/maxima.py"
>>>>>
>>>>> The last two seem to be because of fragile doctests. 
>>>> Can you post the first doctest failure from each failing file?
>>> This is on Sage 3.4.1 (my own build).
>> Ok. Which compiler and host? 3.4.2 is out by the way and 4.0.alpha0 
>> should drop tonight :)
> 
> dagss <at> boksen:~/sage/sage-3.4.1$ uname -a
> Linux boksen 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 
> x86_64 GNU/Linux
> 
> dagss <at> boksen:~/sage/sage-3.4.1$ gcc -v
> Using built-in specs.
> Target: x86_64-linux-gnu
(Continue reading)

Permalink | Reply |
headers
Dag Sverre Seljebotn | 13 May 09:48
Picon
Picon

Re: [Cython] 0.11.2 release schedule?

Michael Abshoff wrote:
> Dag Sverre Seljebotn wrote:
>> Michael Abshoff wrote:
>>> Ok, changing semantics like that makes me queasy, but I assume you guys 
>>> know what you are doing. It seems like a rather deep fundamental change 
>>> for 0.11.1->0.11.2.
>> I think there's no way around it now -- unless Robert wants to make this 
>> 0.12 because of this change alone, it will have to be remedied by a big 
>> warning in the release notes only.
> 
> I did not mean to imply that this discussion should be reopened, just 
> that some people might be a little surprised that a "minor" bug fix 
> breaks their code :)

Well, there's been some discussions about this and in the end it I looks 
like it was decided that minor releases are /not/ simply 
backwards-compatible bugfix releases. Currently they more reflect 
whether the -unstable tree has been merged since the last time or not 
:-), and basically "how significant the upgrade is".

The reason this isn't a problem is because there are seldom bugs of the 
kind which forces users to upgrade in the first place :-)

If something like a critical bug which forces users to upgrade comes 
along and this *does* become a problem I suppose the solution is to 
backport the fix on the 0.11.1 tree and make a 0.11.1.1 release

>>> I have never seen this and I am pretty sure it is unrelated to Cython. 
>>> If you could send me a link to the compressed install.log I could take a 
>>> look. This indicates a problem with libpng.
(Continue reading)

Permalink | Reply |
headers
Robert Bradshaw | 1 May 23:35
Favicon

Re: [Cython] 0.11.2 release schedule?

On May 1, 2009, at 1:00 PM, Dag Sverre Seljebotn wrote:

> Robert Bradshaw wrote:
>> On May 1, 2009, at 9:18 AM, Stefan Behnel wrote:
>>
>> Yes, that would be great if you would do the release managing--
>> definitely would make a mid-May release more feasible.
>
> I'll give it a try.

Great. Thanks.

>>> There are tons of open issues assigned to 0.11.2, though. I don't
>>> expect
>>> many more releases for 0.11.x (maybe a .3, but not necessarily a .
>>> 4), so
>>> they may have to get moved to 0.12. At least, there are no really
>>> critical
>>> issues. Some even seem to be so low priority that we should remove
>>> their
>>> milestone all together. Even some 'wishlist' bugs sound more
>>> important than
>>> some of the 0.11.2 tickets. A minor bug in 0.11 doesn't mean it  
>>> needs
>>> fixing in a 0.11.x release, especially if the fix is not trivial.
>>
>>
>> In my view, non-critical tickets attached to unreleased milestones
>> (especially 0.x.y ones) are fair game for moving around. Please go
>> through the list and move everything you don't think we need by the
(Continue reading)

Permalink | Reply |

Gmane