Wouter Verhelst:
> On Tue, Nov 08, 2016 at 11:05:59AM +0100, Christian Seiler wrote:
>> 30 days within the deep freeze should be plenty enough - and as I
>> said: if the problem is more complicated, just talk to the release
>> team _while the package is still in testing_.
>
> Let's say I'm on holiday (or I get hit by a bus and end up in hospital,
> or I get a major project at work which eats up all my time, or whatnot)
> and I don't notice for a while that a package that I maintain gets an RC
> bug. The automated machinery throws the package out before I have time
> to work on the package again. Now what?
>
> What if I did notice, but fixing the bug takes longer than the 15 days
> (and I agree that we shouldn't release with that bug, so I agree that
> the severity is correct)?
>
I appreciate that you are concerned. However, I think most people and
their packages go through the freeze just fine.
* As James noted; sending an update to the bug will reset the timer.
(Update early, update often - last minute pings might not make it in
time)
* Also, if you do not have time for a given bug, please consider
tagging it "help", so your fellow contributors know that you need
help. That tag shows up on all RC bugs views I know of.
* For more extreme cases (death, mowed by bus, sudden long term
illness, etc), the replacement maintainer can ask for an exception.
(per [freeze policy])
Thanks,
~Niels
[freeze policy]:
"""
The release managers may make exceptions to these guidelines as they see
fit. *Such exceptions are not precedents and you should not assume that
your package has a similar exception*. Please talk to us if you need
guidance.
"""
(Emphasis from original - 3rd paragraph from the top)
https://release.debian.org/stretch/freeze_policy.html
