>- category/functionality, some functions are not working, such as getting errors.
What's the difference with the type/bug? >- category/performance, performance issues fixed or improvements. What's the difference with the type/improvement? How about adding them under the type group? I think it's same with `category`. --- Yong On Mon, 11 Sept 2023 at 19:08, Hang Chen <chenh...@apache.org> wrote: > Hi all, > > I would like to start a discussion about adding a new label type category/* > > There are three labels are supposed to be added > > - category/functionality > - category/reliability > - category/performance > > It could be a good improvement to the labeling system that BookKeeper has > today. > Now, BookKeeper mainly have four label categories > > - type/* - type/bug, type/feature ... > - area/* - area/bookie, area/client ... > - release/* - release/4.14.7, release/4.16.0 ... > - cherry-picked/* - cherry-picked/branch-4.14, cherry-picked/branch-4.16 > ... > > type/*: is mainly to distinguish the issues and PRs are for bug > reporting, bug fix, feature requests, feature support. > > area/*: you can know the issues and PRs that happen on which component > with the component labels, such as an issue with type/bug and > area/client means it's a bug report for the client component. > > release/*: labels are indicating which version the issue/PR has been > fixed or will be fixed depending on if the version is released or not. > > cherry-picked/*: labels are more mainly for BookKeeper committers to > ensure the fixes are cherry-picked to the release branches. The label > only can be added after the cherry-picking is done for a corresponding > branch. So that the release manager can have a list of PRs that should > be cherry-picked. > > In addition to being able to identify which component that the issue, > PR is fixed or enhanced, the category labels will provide more > information about the fix or enhancement for functionality, > reliability, or performance. For most cases, the category labels only > work with type/bug and type/enhancement. > > - category/functionality, some functions are not working, such as > getting errors. > - category/reliability, the function is working for most cases. It > does not work properly in certain specific environments or failures. > e.g. data lost, consumption stuck ... > - category/performance, performance issues fixed or improvements. > > Thanks, > Hang >