On Wed, Dec 13, 2023 at 10:27:20PM +0100, Daniel Gröber wrote:
> On Wed, Dec 13, 2023 at 07:24:49PM +, Holger Levsen wrote:
> > On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote:
> > > That's fine, but in that case this fact should be documented instead no?
> > > Right now there's
control: reopen -1
control: reassign -1 debian-policy
control: retitle -1 please stop mentioning urgency=critical
thanks
On Wed, Dec 13, 2023 at 10:27:20PM +0100, Daniel Gröber wrote:
> On Wed, Dec 13, 2023 at 07:24:49PM +, Holger Levsen wrote:
> > I believe Debian policy should be changed
On Wed, Dec 13, 2023 at 07:24:49PM +, Holger Levsen wrote:
> On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote:
> > That's fine, but in that case this fact should be documented instead no?
> > Right now there's confusion across the docs what criticality levels are
> > available.
On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote:
> That's fine, but in that case this fact should be documented instead no?
> Right now there's confusion across the docs what criticality levels are
> available. Britney.conf and d-policy mention critical/emergency but nothing
> else
Hi Holger,
On Wed, Dec 13, 2023 at 02:19:14PM +, Holger Levsen wrote:
> On Wed, Dec 13, 2023 at 01:55:21PM +0100, Daniel Gröber wrote:
> > > 6.3.2. Selecting the upload urgency
> > mentions only high, medum and low urgency values. Britney also
> > supports critical and emergency. These should
Source: developers-reference
Severity: normal
Hi,
> 6.3.2. Selecting the upload urgency
mentions only high, medum and low urgency values. Britney also
supports critical and emergency. These should be documented as well.
Something like:
- The delays are currently 2, 5 or 10 days, depending on
6 matches
Mail list logo
