Consolidating memory leak related labels in JBS
Lindenmaier, Goetz
goetz.lindenmaier at sap.com
Fri Sep 23 06:30:11 UTC 2022
I appreciate consolidating labels!
What about a11y and accessibility? I don't see a point distinguishing
here, either. But maybe you know more about the background.
I also have to filter for !testbug and !noreg-self if I do not want to
see changes that only touch the test suite.
Would this also be a candidate? But as I understand the noreg-*
labels distinguish more cases that the testbug label did.
Best regards
Goetz
> -----Original Message-----
> From: jdk-dev <jdk-dev-retn at openjdk.org> On Behalf Of Jesper Wilhelmsson
> Sent: Thursday, September 22, 2022 5:36 PM
> To: jdk-dev at openjdk.org
> Subject: Consolidating memory leak related labels in JBS
>
> Hi all,
>
> In JBS we currently have the labels:
>
> memoryleak
> memory-leak
> memory_leak
> Memoryleak
> MemoryLeak
> MemoryLeaks
> leak
> Leak
> leaks
> leakage
>
> All these seems to mainly be used to tag issues concerning memory leaks and
> are used by several teams. No area or group seems to have focused on one
> of these labels, it seems everyone is in agreement that any of these will do
> just fine - judging by label usage in JBS.
>
> Are there any objections to merging all of these into using ONLY
> "memoryleak" and get rid of the rest?
>
> Thanks,
> /Jesper
More information about the jdk-dev
mailing list