Re: systemd-sysv/shim in testing
Cameron Norman <camerontnorman@gmail.com> writes:
> I believe the choices are to repose the question to the TC, now that the
> situation has actually occurred, or begin a General Resolution. As far as
> I understand, a GR would only need a majority since the TC did not really
> make a ruling.
The release team can decide on testing migration schedules and on
release-critical bugs following their normal processes. That was part of
the point of the TC not ruling: the project should follow its normal
processes and do its normal good job of balancing the conflicts between
getting the right software into the next release and keeping the release
stable.
The timing of migration of the new version of systemd to testing, like
questions about testing migration in general, is really a release team
decision. They may want the new systemd to get into testing for broader
testing ASAP, or they may want to use this as an opportunity to test the
upgrade process that we expect stable users to go through (in which case
waiting for systemd-shim may make sense), or they may have some other
opinion or goal. Regardless, it's up to them; this is their bailiwick,
obviously with the opinions of the maintainers of the relevant packages
taken into account.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: