Responses inline below.
On 13 Nov 2017, 8:31 AM +1100, Stefan van der Walt stefanv@berkeley.edu, wrote:
It looks like we have general support for the notion to do one more Python 2.7 release, and to then switch to Python >= 3.5.
🎉
As far as I recall, Egor volunteered to be release manager---thank you!
I recall this too. =)
I think we can hold off a bit on 0.14: our last release was in September, and there are a few PRs in the pipeline near completion. How about we split off the 0.14.x branch beginning of February?
Feb! That seems excessive? I don’t think our bug fix backport releases really count as releases.
Since we're going to be backporting a lot of patches, should I ask Matthias Bussonier to activate
I’m a fan of this idea.
On Tue, Nov 14, 2017, at 22:41, Juan Nunez-Iglesias wrote:
I think we can hold off a bit on 0.14: our last release was in September, and there are a few PRs in the pipeline near completion. How about we split off the 0.14.x branch beginning of February?>
Feb! That seems excessive? I don’t think our bug fix backport releases really count as releases.
How about this, then: Egor, give us a date that you'd like to release (taking into consideration that you'd then need to do the work ;), leaving at least one month before that to finish pending PRs. Stéfan
-
Juan Nunez-Iglesias -
Stefan van der Walt