[Cython] 0.11.2 release schedule?

[Dag Sverre Seljebotn]

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.

>> 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  
> release in two weeks.

Yes, I share this view -- I tend to think of it in the direction of 
time-based release cycles and no so much what it says in trac.

However I like the split between 0.11.x and 0.12 because it helps get 
some kind of sense of what needs to go in which repository -- i.e. does 
it make things unstable, or require something which already went into 
unstable?

I like filing new trivial bugs to the "-devel"-release for this reason.

About "wishlist", I think that just a lot of those bugs should be moved 
out of "wishlist"; feature requests should go there IMO.

Anyway, this is not very important, but I think I'll create a 0.11.3 
rather than mix things into 0.12.

-- 
Dag Sverre