Debian Python Policy - Upgrade Procedure

[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ A ] [ B ] [ C ] [ next ]

# Debian Python Policy
Appendix C - Upgrade Procedure

This section describes the procedure for the upgrade when the default python version is changed in the `unstable` distribution, requiring recompilation of many python-related packages.

1. Selected pre-releases and release candidates of new Python versions are uploaded to Experimental to support pre-transition work and testing.

2. Application and module maintainers make sourceful changes where needed to prepare for the new Python version when needed.

3. Have a long and heated discussion.

4. The Debian Python maintainer and module/application maintainers discuss the readiness for a new default Debian Python version and associated packaging/policy changes. Once there is some consensus, the Python maintainer announces the upgrade and uploads to Unstable.

5. Upload of the python core meta-packages `python`, `python-dev`, `python-doc` and several `python-module`, depending on the new `pythonX.Y`, `pythonX.Y-dev` and so on.

6. The release team schedules rebuilds for packages that may need it. Packages that require additional manual work get updated and uploaded.

[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ A ] [ B ] [ C ] [ next ]

Debian Python Policy