robertwb at gmail.com
Wed May 9 00:16:44 CEST 2012
On Tue, May 8, 2012 at 12:04 PM, Vitja Makarov <vitja.makarov at gmail.com> wrote:
> 2012/5/8 mark florisson <markflorisson88 at gmail.com>:
>> On 8 May 2012 19:36, mark florisson <markflorisson88 at gmail.com> 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. 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
More information about the cython-devel