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

Bug#727708: init system coupling etc.

On Wed, Feb 12, 2014 at 10:35:12PM +0000, Ian Jackson wrote:
> > >    Software outside of an init system's implementation may not require
> > >    a specific init system to be pid 1, although degraded operation is
> > >    tolerable.
> > 
> > This is super vague. What does being "outside of an init system's
> > implementation" mean? What does "degraded operation" mean?
> Yes.  I agree that it's vague.  I'm open to better and clearer
> suggestions.  When I wrote this I was hoping that the policy process
> would be able to refine the details but perhaps that's overoptimistic.

Might we be able define "degraded operation" in terms of BTS severities?
Packages MUST NOT experience Severity:important or greater buggy
behavior with alternate inits as pid 1, for example.

There's still a certain amount of subjectivity in identifying bug
severities, but we've got a lot of experience with them and generally
manage to agree on them. Defining such coupling in terms of BTS
severities is also nice because it makes it easy for us to use our
existing infrastructure to track, over time, how tightly coupled we
become with a particular init system.


Attachment: signature.asc
Description: Digital signature

Reply to: