On Sat, Mar 20, 2021 at 06:52:35PM +0100, Bastian Germann wrote: > Am 20.03.21 um 17:49 schrieb Roberto C. Sánchez: > > Could you request from the release team an exception for this > > bug so that we can deal with it in the next release cycle without > > completely expelling the package in the meantime? > > If you think that is a reasonable request, you can do so. > If you want me to do something about it, I am happy to request the move to > non-free, as suggested. But I am not the maintainer nor an uploader, so the > release managers will synchronize with you beforehand, which is why I did > not file that request.
Quite right. I assumed you were uploader on all the team packages, but it looks like the commentaries have not been updated for a few years. > I think the sooner this is handed in the better. In 2 > weeks the package will be autoremoved and will not have a chance even to > enter non-free after that. > Very true. Another possibility occurred to me. Would you be comfortable lowering the serverity to 'normal' until after the release, then raising the severity again? I believe that we have that latitude within the team and it would not require involving the release team (who are quite busy with a buster point release in the coming week plus the preparations for the next stable release). Regards, -Roberto -- Roberto C. Sánchez
