news 28 Posted June 4, 2017 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, All RC bugs have been tagged with either "stretch-can-defer" or "stretch-will-remove". If a package has an RC bug tagged "stretch-will-remove", then it will be manually removed from stretch next week (unless it is fixed and the fix migrates to stretch before the deadline on Friday, 2017-07-09) You can find all RC bugs tagged "stretch-will-remove" via this link: https://udd.debian.org/bugs/?release=stretch&merged=ign&rtstretch-will-remove=only&fnewerval=7&flastmodval=7&rc=1&chints=1&cdeferred=1&caffected=1&sortby=id&sorto=asc&format=html#results With the deadline for fixes being what it is, please keep in mind that: ======================================================================= * Assume that the Release Team want your package to have at least 2 days in unstable before they are migrated (via a "age-days 2" hint) * Uploads processed /after/ the 13:52 UTC dinstall Wednesday, 2017-06-07 will *not* be able to reach 2 days in testing before the deadline. * Packages uploaded before this deadline will have a very limited time to be tested, so only very small, targeted fixes can be considered. * Accordingly, we are at the point where NMUs have to be without delay to make it in stretch. (Please NMU responsibly) * If your changes are covered by the list in "Please keep changes limited to", then upload first and file an unblock after. A pre-approval round trip will cost us significant time that is better spent having the package in unstable. Uploads with changes not covered by that list will be rejected, so there is no point in asking for pre-approval or unblocks for those changes. Please keep changes limited to: =============================== * RC bugs * Patches for crashes/memory leaks/etc. * Security bug fixes * Regressions compared to jessie or a previous upload to stretch * jessie to stretch upgrade issues * Translation updates If your changes include anything beyond that and an update to d/changelog, then we will probably ask you to reupload without such changes or simply reject the entire changeset. Mini-FAQ ======== Q: What if my upload misses the deadline? A: The upload will not be included in the initial stretch release. - If the package has an unfixed RC bug tagged "stretch-will-remove", the package will be removed from stretch prior to the release. - Otherwise, the package will be included in the release. Please consider whether the bug should be fixed in a stable update (e.g. 9.1) Q: Can an upload after 13:52 UTC dinstall Wednesday, 2017-06-07 still make it into stretch? A: Assume no. Q: Can I assume that my upload will be included if it is unblocked AND and in unstable before 13:52 UTC dinstall Wednesday, 2017-06-07? A: No. We often unblock uploads pre-emptively before buildds and piuparts test have run. If they report back regressions (or simply do not have capacity before the migration deadline), they will stop the migration. Q: My package got a (new) RC bug, which is not tagged "stretch-can-defer" OR "stretch-will-remove". What will happen to it? A: It will generally receive a "stretch-can-defer". For the Release Team, Niels -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlk0Z0IACgkQBUu7n32A ZEJGqw/+Mv4nsTN+7j24lrTCRIARSARfpWDvgvFKk+mfdTmIa5FfcTzcayUjXxVp YZiwQeDG0y0CEs6IMLat75gbXdDQuNF6t1R4P/la1fsPzV4AlBsgzp95srsTI4jz KmTCqbJluNcqF0/cWP8jX/N1njkKLsq41vOa0Fchoo3NsT/p+Bmco8s4A1wNPjWm FLrcpb+7JMGnC2ThFTU0E68lJhIwGMLrevHlhZs8OdKPKdZDwzyFp7AGVmfbejuC i9962QzMxWd3mAb0q55kEEezENmJUeE5jk5n5FrsmFLbzrYUesYO6ey3nueYQuGH Y7xgO4srBciyB2CXutjzRUdXY6GOSofIcqaB89TpssYt6rGDJ6DvA+0I6BtqwbYi F7EOVzOqzJQqeofw2wfbQyYoCXOoKmXrMC8o8kEsgLIUCZm834ymD2x4xvI9BBOM ETmGJSF1i1toZbpZYwvKu4MV2znaPRHkWF+fPu3rwFbCA+quA443COP+w3ZAHxti Q0Wdit8/sAA5jlMKbxAhaxO/nFUrA4L3+O0sG+F5Xd7bVjtbUkuw0JgOTne+QaEC 8dTDmImE0suQPd4v+/ygbT0HdRNMqOZxLBeNDh5PWqElv0U1ZcnE9BHFQs+TWDdd TsHjm4BlqLtVBQuqgFGfNzIQjWTITSZtbsmr/o3u+dow7rRlPIs= =+ilY -----END PGP SIGNATURE----- Share this post Link to post
