[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Status on the stretch release



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

 * A brief status [status]
 * Extended description of selected topics
   * How can you help? [help]
   * RC bugs in general [general-RC]
   * Highlighted RC bugs [highlight-RC]

A brief status: [status]
========================

First off, a list of items with progress:

 * Secure boot support: We got a signature from Microsoft on our shim
   bootloader
 * OpenSSL transition: Done
 * MySQL -> MariaDB transition: Done
 * gcc-5 removal: Done
 * RC bugs (key packages): We went from 150 to 40 RC bugs (since
   2017-02-04)
 * The stretch-backports suite now exists
 * DSA have successfully upgraded several servers including one buildd
   for all architectures except for arm{el,hf}.
 * We are almost done with the "Before the freeze" part of the release
   checklist (just missing some buildds being upgraded to stretch).

Then we got some items that are WIP or where we are stalled:

 * DSA have upgraded a arm{el,hf} buildd to stretch, but it fails to
   boot. At the current time, the cause is not known.
 * Secure boot: We are still waiting for the FTP-masters to add signing
   support in DAK (#821051).
 * We still got 40 RC bugs in key packages and we are getting further
   and further between fixes.
 * We got some pending reviews of the release-notes from the kernel
   team and d-i.
 * We have done some of the binNMUs for updating "Built-Using" headers,
   but we are not done with all of them yet.
 * We still have some pending bugs about issues for upgrades from
   jessie to stretch.


Extended description of selected topics:
========================================

How can you help? [help]
=-=-=-=-=-=-=-=-=-=-=-=-

The "rule of thumb" order for best ways to help:

 * If you(r team) got a request from the release team asking you to
   do something (e.g. review documentation), please carry that out.
   - If you are blocked (e.g. by a bug), please ensure that we are
     aware of that issue.

 * If you (team-)maintain a package with an "stretch-is-blocker" bug,
   please fix that.
   - Please note that new "stretch-is-blocker" tags can appear at any
     time as we review the bug list.

 * If you receive / see an RC bug about issues with the upgrade path
   (often titled "<pkgA>: please add Breaks: <pkgB>"), please fix
   these so we can verify that upgrade path works after that.
   - Sometimes we need multiple fixes to fix an upgrade path.

 * Assist people/teams that are affected by one of the above e.g. by
   triaging bugs, preparing patches, or otherwise handle some of their
   workload.

 * Test upgrades, test packages, test patches.

 * Blog/microblog about what excites you about the upcoming stretch
   release.  Maybe it's the improved hardening, new software that is
   included or  reproducible builds... Whatever it is, remember to
   share it with us, e.g.:
   - via planet.debian.org
   - microblogging a link to your post in micronews.debian.org (see how
     to in the "Contribute" page in that site)
   - contributing a post to bits.debian.org (for example, for team
     posts)

RC bugs in general: [general-RC]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

We are approaching the final phase of the freeze.  Among other that
means that we are left with a lot of RC bugs that are less trivial to
solve.  Even so we ask you to put an extra effort into helping us
triaging and solving these last bugs.

If you have multiple RC bugs on your radar, please prioritise fixing
upgrade paths, regressions from jessie and bugs that block other
people from working on their bugs/release tasks (see the "How can you
help?" above).

The current list of unfixed RC bugs in key packages affecting both
unstable and testing can be found in [UDD-QUERY]

In the absence of a fix, we will eventually have to defer the fix to
buster (or a point release) save for a select few bugs.  We would
prefer not having to do that excessively but on the flip side, nobody
wants the freeze to last for ever.

Highlighted RC bugs: [highlight-RC]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

These are some RC bugs where we would like to add a few words:

 * #849099/#849098/#848368 (llvm-toolchain-*): Sylvestre is working
   on these, but unfortunately we are hit by a FTBFS issue on some
   architectures.

 * #665199 (openldap): We have two patches posted (one for stretch
   and one for jessie) to the maintainer scripts.  Additional reviews
   very welcome.

 * #831007 (tar): Bdale is working on a debdiff pulling upstream
   commits to close this bug.

 * #859262 (synaptic): Accessibility issue where the screen reader
   (orca) freezes and appears to be a regression since jessie.

 * #852622/#839314 (xcffib): One bug fixed in unstable, but cannot
   migrate due to another bug in unstable (that does not affect
   testing).
     Either a tpu fix for #852622 or a patch for #839314 would help us
   resolve this.

 * #781155 (openbsd-inetd): If not resolved soon, we are considering a
   removal from testing.

For the Release Team,
  Niels

[UDD-QUERY]
https://udd.debian.org/bugs/?release=stretch_and_sid&merged=ign&keypacka
ges=only&fnewerval=7&flastmodval=7&rc=1&chints=1&ctags=1&cdeferred=1&crt
tags=1&sortby=id&sorto=asc&format=html#results


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAljxy5oACgkQBUu7n32A
ZELWYBAAoOJa36rxa/AIWEqRpdW3/dbyGMb7Uqi+9U5MnvuHxOMhRDl2Eb7qldoC
BVDNSvnofAqA17cmX0T1he227qwj6gE+YfDGlHtAiFtYRD5y2zvQglE7aZmYgmmh
BcYc1Ksz4C8HUJxygs72G6JzEbQk6jrBykJX9gHiP6hZkwNs6Ive2MgGMO/96EWa
GRcn0vpeOICWnYxg7GDuWY84BTgsE1zeqZ+ent2+jOC7uDuIkyYmwOkM2DaTZ/Lm
7lEO/kJ8Ewbjtu+tlM3UcmNlxyikT5Lx3U4P2PLgQcX/P8nA0iCTfH4e/YtV14N7
KkCBuz6MM0GVb2hMSonOeh1N83rbTorDxvVsgF6fZTHzs98DzdfTi/icNmjsHNdI
oRMX+ZcAWFOQkrzqxcRQcsBxVpig7RwGv4mUzG4rVb0j3FP2nivop4eZ6u6pohiN
4OQaUwVGanJSXusFQoAvQePguuqOm3As1alSTaLXlJqsBYvQU4E7/ebVZvJ5qRAe
r0/3EV2r+hPUF2pzbUQQ82kqfBTvFD/LXfazumMQKF0NdSxNDbOgAiaCCBSjCgci
EKXVVLgscAizb8lXz/5JazpZEb9zWQjY1yOnnUpxVwSrzth+/YWqe7KXCrI7j9Od
bJig9StXo6kVvCQb2FedaJKVKeC7ECOHtqa4leS1ewMJAqUaKlE=
=erTr
-----END PGP SIGNATURE-----


Reply to: