[Python-Dev] Some data points for the "annual release cadence" concept
Matthias Klose
doko at ubuntu.com
Wed Jun 13 04:27:32 EDT 2018
More information about the Python-Dev mailing list
Wed Jun 13 04:27:32 EDT 2018
- Previous message (by thread): [Python-Dev] Some data points for the "annual release cadence" concept
- Next message (by thread): [Python-Dev] [RELEASE] Python 3.7.0rc1 and 3.6.6rc1 are now available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 2001. In 2015 they changed the versioning schema, but it's still one major release per year.
- Previous message (by thread): [Python-Dev] Some data points for the "annual release cadence" concept
- Next message (by thread): [Python-Dev] [RELEASE] Python 3.7.0rc1 and 3.6.6rc1 are now available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list