ESC meeting minutes: 2025-07-03

[Ilmari Lauhakangas]

On 7/3/25 17:47, Mike Kaganski wrote:
> On 7/3/2025 7:35 PM, Stephan Bergmann wrote:
>> * Bisected bugs open: keyword 'bisected'
>>    + more accurate - down to a single commit.
>>    + http://bit.ly/2dyIfDy
>>    +
>>
>>      done by:
>>         vijaya chandra         4
>>         Xisco Fauli            4
>>         Weghorn, Michael       1
>>
>>
>> * Bibisected bugs open: keyword 'bibisected'
>>    + http://bit.ly/2cSCXlS
>>    +
>>
>>      done by:
>>         vijaya chandra         4
>>         Xisco Fauli            4
>>         Weghorn, Michael       1 
> 
> 
> Is there any reason to still have that "bisected" vs. "bibisected" 
> difference? IIUC, in the beginning, the bibisect repos were not as fine 
> as now, and it could make sense. I don't believe that we have a real 
> option to do bisects other than bibisects? And anyway, if there will be 
> a case where there would be a difference, it would be explained in the 
> comment - I don't think anyone would actually *expect* to check keywords 
> to know that.
> 
> A proposal is to drop the "bibisected" keyword from Bugzilla, and the 
> respective section from the minutes.

In practice we have used bibisected alone, when the result is a range.

https://wiki.documentfoundation.org/QA/Bibisect#General_Instructions

Step 3 at the end of that section:

"Replace the keyword bibisectRequest with bibisected and bisected (only 
include the last one, if you found the exact commit and not just a range 
of commits)"

Ilmari