![]() ![]() For the next thirty six months (3 years) it receives security. ![]() MacOS) are made approximately every other month. Updates and full releases (sources and installers for Windows and During the first twenty four months (2 years) it receives bugfix.If necessary) and conclude with the release of the final release ofĢ years of full support, 3 more years of security fixesĪfter the release of Python 3.X.0, the 3.X series is maintained for The final two months are spent on two release candidates (or more,.Where no new features can be added but bug fixes are still The following three months are spent on four versioned beta releases.The next seven months are spent on versioned alpha releases whereīoth new features are incrementally added and bug fixes are included.The first five months overlap with Python 3.(X-1).0’s betaĪnd release candidate stages and are thus unversioned.This PEP proposes that Python 3.X.0 will be developed for around Implementation Seventeen months to develop a feature version Such that feature versions are released predictably every twelve months, This change accelerates the release cadence This document describes a change in the release calendar for Python Slow down releases but don’t freeze feature development with Beta 1.Keep “4 betas over 4 months and a final month for the release candidate”.Double the release cadence to achieve 9 months between feature versions.Keep the current 18 month release cadence.Other policies may depend on the release cadence.2 years of full support, 3 more years of security fixes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |