Hi Nick,

On 21-12-2021 20:52, nick black wrote:
well, as i noted above, this use case certainly isn't the
standard way growlight will be used (although it's a valid one,
and one worth fixing -- this was a valuable exercise, and i
appreciate autopkgtests spotting this regression!). so it's not
very important to users...but at the same time, it was
considered important enough to drop the package from testing =].
so i guess i'm getting a bit of a mixed message here.

I understand why you say that.

the way i read it, this was critical to fix for the
autopkgtests/transition regime, and relatively unimportant for
most users. so i agree, we can do without the versioned dep.
thanks for walking me through your thinking.

But indeed, this. We (the Release Team) have decided that there's two items RC that are relevant for this case: autopkgtest failure and out-of-sync for too long. What's the *reason* for the autopkgtest failure hardly matters as the outcome for nearly everything is black/white due to automation. I mean an autopkgtest that fails because a text changes in output somewhere (yes, I see this a lot), is similarly blocking as segfault during every use. We do accept exceptions once in a while, but the baseline is, it should work. We try to have a balance here; there's a carrot (reduced migration and less rules during the freeze) and a stick (it has to work, otherwise....).

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to