markflorisson88 at gmail.com
Wed May 9 10:33:27 CEST 2012
On 9 May 2012 07:41, Stefan Behnel <stefan_ml at behnel.de> wrote:
> Robert Bradshaw, 09.05.2012 00:16:
>> On Tue, May 8, 2012 at 12:04 PM, Vitja Makarov wrote:
>>> 2012/5/8 mark florisson:
>>>> On 8 May 2012 19:36, mark florisson wrote:
>>>>> Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
>>>>> picks over its own fixes into the release branch (at least Stefan,
>>>>> since your fixes pertain to your newly merged branches and sometimes
>>>>> to the master branch itself). This branch should not be merged back
>>>>> into master, and any additional fixes should go into master and be
>>>>> picked over to release.
>>>>> Some things that should still be fixed:
>>>>> - nonechecks for memoryviews
>>>>> - memoryview documentation
>>>>> - more?
>>>>> We can then shortly-ish after release 0.17 with actual features (and
>>>>> new bugs, lets call those features too), depending on how many bugs
>>>>> are still found in 0.16.1.
>>>> TBH, if we're actually close to a major release, the usefulness of a
>>>> bugfix release is imho not that great.
>>> There are some fixes to generators implementation that depend on
>>> "yield from" that can't be easily cherry-picked.
>>> So I think you're right about 0.17 release. But new features may
>>> introduce new bugs and we'll have to release 0.17.1 soon.
>> If we're looking at doing 0.17 soon, lets just do that.
> I think it's close enough to be released. I'll try to get around to list
> the changes in the release notes (and maybe even add a note about alpha
> quality PyPy support to the docs), but I wouldn't mind if someone else was
> quicker, at least for a start. ;)
>> In the future,
>> we could have a bugfix branch that all bugfixes get checked into,
>> regularly merged into master, which we could release more often as
>> x.y.z releases.
> +11. We have the release branch for that, it just hasn't been used much
> since the last release.
Yeah, I like it too. It's much easier than cherry-picking stuff over
in a large history, where fixes may depend (partially) on features.
> I also don't mind releasing a 0.16.1 shortly before (or even after) a 0.17.
> Distributors (e.g. Debian) often try to stick to a given release series
> during their support time frame (usually more than a year), so unless we
> release fixes, they'll end up cherry picking or porting their own fixes,
> each on their own. Applying at least the obvious fixes to the release
> branch and then merging it into the master from there would make it easier
> for them.
Debian stable? :) Good point though, I think we can manage that.
> cython-devel mailing list
> cython-devel at python.org
More information about the cython-devel