Re: [Python-Dev] Some data points for the "annual release cadence" concept

> On 15 Jun 2018, at 13:00, Nick Coghlan wrote: > > On 14 June 2018 at 06:30, Ronald Oussoren > wrote: >> On 13 Jun 2018, at 15:42, Nick Coghlan > > wrote: >> >> Yeah, pretty much - once we can get to the point where it's routine for

Re: [Python-Dev] Some data points for the "annual release cadence" concept

On 14 June 2018 at 06:30, Ronald Oussoren wrote: > On 13 Jun 2018, at 15:42, Nick Coghlan wrote: > > Yeah, pretty much - once we can get to the point where it's routine for > folks to be building "abiX" or "abiXY" wheels (with the latter not actually > being a defined compatibility tag yet, but

Re: [Python-Dev] Some data points for the "annual release cadence" concept

> On 13 Jun 2018, at 15:42, Nick Coghlan wrote: > > On 13 June 2018 at 02:23, Guido van Rossum > wrote: > So, to summarize, we need something like six for C? > > Yeah, pretty much - once we can get to the point where it's routine for folks > to be building "abiX" or

Re: [Python-Dev] Some data points for the "annual release cadence" concept

On 13 June 2018 at 02:23, Guido van Rossum wrote: > So, to summarize, we need something like six for C? > Yeah, pretty much - once we can get to the point where it's routine for folks to be building "abiX" or "abiXY" wheels (with the latter not actually being a defined compatibility tag yet,

Re: [Python-Dev] Some data points for the "annual release cadence" concept

On 12.06.2018 14:38, Nick Coghlan wrote: Since we last seriously discussed potential release cadence changes back in 2012 (with PEPs 407 and 413 [2,3]), that means JEE joins GCC switching to an annual release cadence from GCC 5 back in 2015 (see [4]), no, GCC is doing yearly releases since

Re: [Python-Dev] Some data points for the "annual release cadence" concept

On 12.06.2018 18:23, Guido van Rossum wrote: So, to summarize, we need something like six for C? there is https://github.com/encukou/py3c ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev

Re: [Python-Dev] Some data points for the "annual release cadence" concept

So, to summarize, we need something like six for C? On Tue, Jun 12, 2018 at 5:38 AM, Nick Coghlan wrote: > Hi folks, > > Given the discussion of adopting an annual release cadence at the language > summit this year [1], this recent Jakarta (nee Java) EE announcement caught > my attention:

[Python-Dev] Some data points for the "annual release cadence" concept

Hi folks, Given the discussion of adopting an annual release cadence at the language summit this year [1], this recent Jakarta (nee Java) EE announcement caught my attention: https://www.eclipse.org/ee4j/news/?date=2018-06-08#release-cadence JEE are switching to an annual update cadence for the