I agree that tackling real issues in a timely manner is super important. That’s why I think it’s important to be judicious in labeling issues as “bugs”. When the queue becomes too noisy, people learn to ignore it and important things get missed. When given the choice between too much noise and too little signal, I tend to err on the side of eliminating the noise so that at least we develop the habit of looking at whatever does come through.
I’m glad to see all the issues being filed and all the accompanying activity. I just think we should be clear on how we label things so everyone knows how to prioritize. Mike On Thu, Jan 16, 2025 at 11:26 PM Eric Maynard <eric.w.mayn...@gmail.com> wrote: > No, actually I don't think we need to argue much. We should try to label > things correctly and the difference between what is a bug and what is not a > bug is typically evident. > > This is a bug, <https://github.com/apache/polaris/issues/813> and this is > not <https://github.com/apache/polaris/issues/773>. Both of these are > legitimate issues, but how they are labelled is important. > > On Thu, Jan 16, 2025 at 11:20 PM Robert Stupp <sn...@snazy.de> wrote: > > > We can argue a long time about labels and their usage and about the > > formal definition of those. > > > > What I think really matters is that the issues, especially real bugs, > > with security issues being the absolute #1 priority, are tackled in a > > timely manner. > > > > On 17.01.25 06:00, Jean-Baptiste Onofré wrote: > > > Hi Mike > > > > > > I agree, the bug label should mean: this is something breaking > > > *compared* to a previous commit (as we don't have release yet :)). The > > > GH Issues considering a "bug" not related to a previous commit is an > > > "improvement" to me: it's not a bug introduced on top of a previous > > > commit but more an "general concern/bug" we have in mind, so an > > > improvement on the existing. > > > > > > To sum-up: > > > - we should use "bug" for issue introduced by a commit after another > > > commit (history) > > > - we should use "improvement" for issue/improvement we want to > > > implement (it could be considered as a bug from a personal standpoint > > > but not related to project history) > > > - we should use "new feature" for new functionality we want to > > > implement in the project > > > - we should use "proposal" for design/MVP > > > > > > Regards > > > JB > > > > > > On Thu, Jan 16, 2025 at 10:56 PM Michael Collado < > collado.m...@gmail.com> > > wrote: > > >> Hey folks > > >> > > >> There are over 40 issues with the "bug" label in github right now, > many > > of > > >> which are not actually bugs, but seem to me like personal preferences > or > > >> possible improvements. A lot of these issues seem like reasonable or > > good > > >> changes to me, but I think we should reserve the "bug" label for > things > > >> that are actual bugs. Can we remove the bug label from issues that > > aren't > > >> actually broken? > > >> > > >> Mike > > > > -- > > Robert Stupp > > @snazy > > > > >
