Release update: Mandatory 10 day delay for migrations and other upcoming events
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
We have past the 5th of December and all migrations delays are now 10
days by default as announced in [1]. Should your upload to unstable
include security fixes or fixes for severe bugs, we file an unblock
bug asking for us to lower the required age.
Future milestone dates in the stretch freeze
============================================
This is the second of four milestones for the stretch freeze[2]. The
Release Team maintains a calendar of these at [3] along with other
important dates. The next milestones are (in order):
Jan 5: soft freeze
- ------------------
Deadline for:
* New (source) packages in stretch
* Letting packages re-enter stretch (if they have been removed)
Updates to existing packages in stretch will continue as normal.
Remember:
* New packages must be in testing before January 5th.
* With the mandatory 10-day delay, the latest day for the upload is
/at least/ 10 days earlier.
* Delays caused by RC bugs (even in other packages), lazy FTP-masters or
a long NEW queue (etc.) are *not* an excuse to be late.
Feb 5: Full freeze
- ------------------
Freeze for stretch:
* All changes to stretch will require approval.
* Use "reportbug release.debian.org" for requesting unblocks.
Remember:
* Uploaded changes must be in testing before February 5th
* With the mandatory 10-day delay, the latest day for the upload is
/at least/ 10 days earlier.
* Delays caused by RC bugs other packages, slow buildds,
"C-x M-c M-butterfly" (etc.) are *not* an excuse to be late.
You can also find the dates and their descriptions in our calendar[3].
We will keep you updated as the freeze progresses.
For the Release Team,
Emilio and Niels
[1] https://lists.debian.org/debian-devel-announce/2016/07/msg00002.html
[2] https://release.debian.org/#release-dates
[3] https://release.debian.org/release-calendar.ics
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlhJCNUACgkQBUu7n32A
ZEI6iA/+Jt4DJBpoDbCQzSpq/RAheG3jvkozOabYlpg/h6EesPFZJsVa6Vxa5qRZ
Cqbip5VnDhSbhBCpFQ+kLLL9zUS2sx0RxPju1IDlm4KEb3P8RgPfPTR6S2ztjTw6
8zOcfBKKOMHvenvetw5chLIMdcaCxBF6giI+X7PmNI9OfnC4TC+OU24bcWUMTEYI
JVMq0FC/IyuQTc9cWMnKMbQlzpbHWMlem4I7Fb7IxmaI3E4PDRsA4gH39jjwk/L3
PHYSuhmXJlAoIDumD/PPR3sKWkVti70NEphjjxQS8l9k8MRp4eWm7dea7jyjH2PR
wgeibH7Nd1BHF2g52GT5hlPXkh24+hNFA77bxKaw90e9Uh7niDaZjfz2CpGuDgsb
HAzY/R+jXMALYVk0G6PkCqRWotgeHM9u53Y8KCajBsZJnkQdmcI9lUebbDfoQqij
s1kCsVzfd0DuQuY+gtt0g18RI+KFSy8aK72QOs2Sfwfbo0ZC5qioLm2XA6GjHNjq
L7/Li5AitXbc1gpdc772u6KydKg4Myp2RvdzAW5Ch00XV+8yGJqW8qdblUMZZgQB
NltDlA33P/zvZbLm0EfoqDpG/85xPitIfT8/3YPTBUkA3twu0Ydg+TJ55E5wzk6R
LsZxR32soCITeXkuSeek1E1nnnV54MpNwF8VdaEaIAKJ1bX6fx8=
=0UzJ
-----END PGP SIGNATURE-----
Reply to: