Re: [PROPOSAL] Improve our "collaboration schema"

I agree with most points. But I'm not in favor of such strict and potentially enforced rules like "(at least) 2 days". Also not in favor of "all comments must be resolved", because some comments add descriptive value for later - resolving those comments renders those invisible and hard to inspe

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: [PROPOSAL] Improve our "collaboration schema"

Hi Mike Yes agree to fix bug faster than 2 days. I was more thinking about improvements or new stuff. If we have a consensus, I’m happy to create a PR to update the contributing guide. Thanks ! Regards JB Le ven. 17 janv. 2025 à 06:20, Michael Collado a écrit : > Hi JB > > This is a great top

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: [PROPOSAL] Improve our "collaboration schema"

Hi JB This is a great topic and worth spending time on. Naturally, we want to move fast and get things out quickly, but it’s also important that everyone has a chance to weigh in on changes. This is easy to miss when we’re spread across so many time zones and some groups are working while others a

Re: Next steps for design discussion of Apache Polaris Catalog Federation

Hi folks Thanks Dennis for the meeting yesterday and thanks everyone for your participation. Here's the record: https://drive.google.com/file/d/1IrVZiJHACSIUf8ckvB30Hderrq8LAJMN/view?usp=sharing Thanks ! Regards JB On Fri, Jan 10, 2025 at 3:36 AM Dennis Huo wrote: > > Hello! > > I wanted to k

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

[PROPOSAL] Improve our "collaboration schema"

Hi folks, It's great to see s much activity on Apache Polaris right now ! By experience, this high activity can introduce frustration in the community because contributors might be "lost" or have the feeling of missing important changes/proposals. I propose some good practices we could use t

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

Use of the "bug" label in Github issues

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 t

Re: Next steps for design discussion of Apache Polaris Catalog Federation

Recording and AI Notes I don't pay for the enhanced notes... maybe I should https://fathom.video/share/xDtaN_YsssoxcYZRGenrWzzCsj6J_NSr Apache Polaris - Catalog Federation Meeting - January 16 *VIEW RECORDING - 73 mins (No highlights)*