(original) (raw)
On Mon, Mar 10, 2014 at 8:04 AM, Steven D'Aprano <steve@pearwood.info> wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
If Python 4 is a conservative release, I don't see any reason to bump
the major version number until after Python 3.9.
and why even then?
Perhaps we need a long-term schedule?
why not:
3.5: August 2015
3.6: February 2017
3.7: August 2018
3.8: February 2020
3.9: August 2021
3.10: February 2023
3.11 August 2023
3.12 February 2024
....
version numbering is not decimal -- a bump to 4.0 should mean \_something\_
(Though from the above, we've got a few years before we need to worry about that!)
-Chris
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov