Reword lifespan to make it clearer.
This commit is contained in:
parent
51c49af1b7
commit
b0dfcb30df
|
@ -34,10 +34,11 @@ Release Manager and Crew
|
|||
3.2 Lifespan
|
||||
============
|
||||
|
||||
3.2 will receive bugfix updates approximately every 4-6 months until
|
||||
one release after the release of 3.3.0 final. After that, security
|
||||
updates (source only) will be released until 5 years after the release
|
||||
of 3.2 final, which will be February 2016.
|
||||
3.2 will receive bugfix updates approximately every 4-6 months for
|
||||
approximately 18 months. After the release of 3.3.0 final (see PEP
|
||||
398), a final 3.2 bugfix update will be released. After that,
|
||||
security updates (source only) will be released until 5 years after
|
||||
the release of 3.2 final, which will be February 2016.
|
||||
|
||||
|
||||
Release Schedule
|
||||
|
|
|
@ -34,10 +34,11 @@ Release Manager and Crew
|
|||
3.3 Lifespan
|
||||
============
|
||||
|
||||
3.3 will receive bugfix updates approximately every 4-6 months until
|
||||
one release after the release of 3.4.0 final. After that, security
|
||||
updates (source only) will be released until 5 years after the release
|
||||
of 3.3.0 final, which will be September 2017.
|
||||
3.3 will receive bugfix updates approximately every 4-6 months for
|
||||
approximately 18 months. After the release of 3.4.0 final, a final
|
||||
3.3 bugfix update will be released. After that, security updates
|
||||
(source only) will be released until 5 years after the release of 3.3
|
||||
final, which will be September 2017.
|
||||
|
||||
|
||||
Release Schedule
|
||||
|
|
Loading…
Reference in New Issue