[Pkg-sysvinit-devel] What should we do about sysvinit in unstable?

[Henrique de Moraes Holschuh]

On Sat, 25 Oct 2014, Petter Reinholdtsen wrote:
> I added the latests NMUs to git and uploaded the current set of
> changes to experimental after confirming that it could boot at least
> one machine.  When I started uploading to experimental in April, I
> expected to have time to get the changes tested and ready for unstable
> fairly soon, and get all the changes into unstable before Jessie
> froze.  That obviously did not happen, and I now wonder how we should
> move forward.
> 
> The package in unstable (2.88dsf-53.4) is the last of a series of
> NMUs, and similar NMUs were done in experimental.  The package in
> experimental (2.88dsf-56) now contain the changes from all the NMUs
> done so far, after my upload today.  But I suspect we should not
> upload the experimental package to unstable this late in the release
> cycle.  There are not many changes, but I suspect the release managers
> might be a bit reluctant to accept these changes.

...

> What do the rest of you think is the best way forward?

Can't we just ask the release managers?  They will ask "what is important in
that release?", so if we have a good answer to that question...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh