Re: labels on GitLab

[Jonas Hahnfeld]

Am Dienstag, den 12.05.2020, 16:58 +0200 schrieb Valentin Villenave:
> On 5/12/20, Jonas Hahnfeld <address@hidden> wrote:
> > In my opinion, there are currently far too many labels on GitLab.
> 
> Well, we used to say `Labels are cheap’ back when we were using Google Code…
> 
> > please do not create new labels out of thin air for now.
> 
> Not entirely out of thin air. I’ve actually decreased the number of
> concurrent labels in use, by merging midi with MIDI, warning with
> Warning, musicxml2ly with musicxml, Build with Type::Build and so on.
> (Case-sensitivity in this instance is cumbersome, as you can see from
> the number and inconsistency of fixed_ and Fixed_ prefixed labels.)
> 
> I have indeed created a new label for type conversion issues, which
> seemed appropriate, and another one for SVG output. This is the sort
> of thing some of us used to find useful a dozen years ago; it may be
> less so today but that remains to be seen.
> 
> > Instead we should first contemplate on what we
> > really need and configure this appropriately. (Adding a label for every
> > possible warning that could be fixed is not helpful.)
> 
> That is not my intent.
> 
> V.

And I just saw you changed prioritized labels. This breaks the ordering
in merge requests, so I'm going to revert this now. I'd really hope we
can discuss things before changing...

Jonas

signature.asc
Description: This is a digitally signed message part