On 4 October 2015 at 00:31, Barry Warsaw wrote:
> It's almost as if there's a Linux Cabal[*] dividing and conquering!
Who, us? :)
(Actually, mostly *not* me - I'm mainly a cheerleader, while folks
like Slavek Kabrda, Robert Kuska, Petr Viktorin, Matej Stuchlik, Miro
Hroncok, Thomas Spura, and ev
On Oct 03, 2015, at 11:28 PM, Nick Coghlan wrote:
>We also looked at trying to land 3.5 for this month's Fedora 23
>release (which would have involved bringing the pre-releases into
>Fedora Rawhide), but decided it more sense to prioritise further work
>on the Python 3 migration instead.
It's alm
On 3 October 2015 at 05:41, Ned Deily wrote:
> On Oct 2, 2015, at 10:20, R. David Murray wrote:
>> That said, I do feel the amount of pre-release testing, even in the beta
>> part of the cycle, has increased steadily in the past two or three
>> releases, which is great to see.
>
> Yes, it has. A
On 10/2/2015 3:41 PM, Ned Deily wrote:
On Oct 2, 2015, at 10:20, R. David Murray
wrote:
On Thu, 01 Oct 2015 22:24:18 -0400, Ned Deily wrote:
Another change has been to add a fourth beta and drop the third
release candidate. My gut feeling from the past several releases
is that a lot of featu
On Oct 2, 2015, at 10:20, R. David Murray wrote:
> On Thu, 01 Oct 2015 22:24:18 -0400, Ned Deily wrote:
>> Another change has been to add a fourth beta and drop the third
>> release candidate. My gut feeling from the past several releases is
>> that a lot of feature code does not get checked in
On Thu, 01 Oct 2015 22:24:18 -0400, Ned Deily wrote:
> Another change has been to add a fourth beta and drop the third
> release candidate. My gut feeling from the past several releases is
> that a lot of feature code does not get checked in until close to the
> b1 feature code cutoff so that ext
FYI - I've just updated PEP 494 with a fleshed-out 3.6.0 release schedule. The
3.6 schedule is generally similar to the successful 18-month development and
release cycle used in recent releases but with a few significant changes. The
main difference is that the 3.6 schedule takes advantage of
