[Cython] Bugfix release
vitja.makarov at gmail.com
Sun Sep 11 16:13:38 CEST 2011
2011/9/11 Stefan Behnel <stefan_ml at behnel.de>:
> Stefan Behnel, 11.09.2011 13:33:
>> Robert Bradshaw, 11.09.2011 07:54:
>>> On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov wrote:
>>>> Are we going to make a bugfix release?
>>>> There are some critical bugs in 0.15, T725 for example.
>> Yes, and some others.
>>>> Think we should port fixes back to 0.15 and then release it as 0.15.1
>>> +1 to another release soon. Is there anything in the devel branch
>>> that's not ready to go out?
>> Yes, the current state of my decorator changes breaks code in Sage. I
>> wouldn't know of anything else, so maybe it's enough to back those changes
>> out from a branch and otherwise keep the state that we have now.
> ... especially given that the list of fixes that are scheduled for the next
> release is not exactly short, and some fixes spread over more than one
> commit, so there'd be a lot to merge over.
> A problem with the current master branch is that we already dropped support
> for Py2.3 in it...
> I see two ways to get a release out: create a branch from the current master
> and remove from it what we don't consider stable (or 'right' for that
> release), or merge the most important and easily mergeable changes over to
> the current release branch for 0.15.1 and leave the rest to a
> not-so-far-in-the future 0.16.
> Personally, I vote for the latter, because I think we should rather try to
> get 0.16 out soon and not put too much work into 0.15.1. There were enough
> changes in master (and potentially some more in the open pull requests) to
> merit a 0.16. And I certainly wouldn't mind keeping the list of changes in a
> main release a little shorter.
+1 for second option, What about 2.3 support in 0.15.1?
More information about the cython-devel