Re: Use of the "bug" label in Github issues

I agree that the templates can improve -- but we can and should remove the bug label from things that aren't actually broken even after an issue is filed. On Fri, Jan 17, 2025 at 3:55 AM Jean-Baptiste Onofré wrote: > Hi Alex > > Fully agree: I think we should change our GH templates here and at

Re: Use of the "bug" label in Github issues

Hi Alex Fully agree: I think we should change our GH templates here and at least give “free” fields to the users. I would be more than happy to propose a PR to update the templates and “relax” the fields for the user. Regards JB Le ven. 17 janv. 2025 à 12:34, Alex Dutra a écrit : > Hi, > > If

Re: Use of the "bug" label in Github issues

Hi, If there are issues incorrectly labeled as bugs, that's maybe also because we don't give many choices to users; when opening an issue, our templates are very opinionated and only offer 3 options: "Bug report", "Feature request", and "Report a security vulnerability" (with too many fields to fi

Re: Use of the "bug" label in Github issues

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

Re: Use of the "bug" label in Github issues

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é w

Re: Use of the "bug" label in Github issues

On 17.01.25 08:26, Eric Maynard 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. Well, then let's stop arguing. This is a bug,

Re: Use of the "bug" label in Github issues

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, and this is not

Re: Use of the "bug" label in Github issues

Good point, it makes sense to me. Regards JB Le ven. 17 janv. 2025 à 06:51, Eric Maynard a écrit : > I would also suggest that “bug” can be used when functionality does not > match the docs, the spec, etc. > > On Thu, Jan 16, 2025 at 9:00 PM Jean-Baptiste Onofré > wrote: > > > Hi Mike > > > >

Re: Use of the "bug" label in Github issues

I would also suggest that “bug” can be used when functionality does not match the docs, the spec, etc. On Thu, Jan 16, 2025 at 9:00 PM 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 rele

Re: Use of the "bug" label in Github issues

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

Re: Use of the "bug" label in Github issues

+1. Always good to put more thought into existing issues. Yufei On Thu, Jan 16, 2025 at 1:56 PM Michael Collado 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 > possibl