The TC had an IRC meeting yesterday [0], and I (was) volunteered to wrap up the different outcome possibilities, which would help forming our opinions. Not all these options are exclusive, or would need an actual TC decision.
Here we go: A) 'global' stays maintained as it currently is. This would imply: - no new 'global' upstream release before stretch, - no 'htags removal' warning in stretch, - possibility for the maintainer (and/or other interested parties) to start maintaining a 'global6'; this wouldn't offer any guarantee for a more recent version of 'global' in stretch. This would also imply having two 'global' packages in certain suites. B) A fresher version of 'global' is uploaded to experimental 'soon' (with or without interested parties' help; with or without a TC decision) This would imply: - any interested party would file (and close) Debian bugs for issues and regressions (with appropriate severities), to make the 'fitness for a stable release' assessment easier, and earlier. C) After the release of stretch, a fresher version of 'global' is uploaded to unstable with the explicit goal of making it available in buster. This would imply: - any interested party would file (and close) Debian bugs for issues and regressions (with appropriate severities), to make the 'fitness for a stable release' assessment easier. - after migration to testing, this would make the fresher version of 'global' available for backporting to stretch-backports. - the version of 'global' released in stretch could carry 'htags removal' warnings; D) A fresher version of 'global' is uploaded to unstable 'soon', targetting stretch (with or without interested parties' help; with or without a TC decision) This would imply: - overruling the 'global' maintainer's decision (§6.1.4, implies 3:1 majority in a TC vote); - any interested party (including the maintainer) would file (and close) Debian bugs for issues and regressions (with appropriate severities), to make the 'fitness for a stable release' assessment easier. - that this fresher version of 'global' would reach 'fit for release' status before the Stretch release. E) the 'global' package is handed to other maintainer(s) This would imply: - overruling the 'global' maintainer's decision (§6.1.4, implies 3:1 majority in the TC vote); -- Cheers, OdyX [0] http://meetbot.debian.net/debian-ctte/2016/debian-ctte. 2016-11-22-16.59.html
signature.asc
Description: This is a digitally signed message part.