[Proposal] Additional labels and a label suggestion tool

[Alena0704]

Description

I suggest adding a few labels to make issues and PRs easier to browse and filter.

PR availability for issues

It would be useful to see directly in the issue list whether an issue already has an associated PR. A has-pr label could make this visible without opening each issue and allow filtering by PR availability.

Ideally, this label would be applied automatically. We should also agree on how to handle it when a PR is closed without merging while the issue remains open.

Topic labels for issues and PRs

At a minimum, I propose adding:

• postgres optimizer — PostgreSQL query optimizer topics; especially it is strange that we don't have it since Orca label is available.
• vacuum — VACUUM and autovacuum;
• statistics — statistics collection and usage, including ANALYZE.

Other potentially useful labels:

• wal — write-ahead logging;
• backup — backup-related topics.

These labels would help contributors find related issues and PRs by subsystem and identify changes relevant to their interests or expertise.

Label suggestion tool

It could also be useful to introduce a tool that suggests relevant labels based on the title and description of an issue or PR.

The tool could recommend existing labels when an issue or PR is opened or updated, leaving the final choice to the author or maintainers. This could make labeling more consistent and reduce manual work.

Discussion

• Any suggestions for naming or other missing categories?
• Would a label suggestion tool be helpful, and are there any existing tools we could use?

Use case/motivation

No response

Related issues

The topic of additional labels and automated bug classification has already come up in Discussion #1952 — Continuous SQLancer fuzzing, which proposes a sqlancer label and classification using type: Orca or planner.

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[jianlirong]

I strongly support this proposal!

In our internal development workflow, we have been using labels for years, and they have proven very useful in practice. We use them not only to categorize issues, but also to help assign work to the right engineers and track issues targeted for upcoming releases.

For example, by labeling issues with the target release version, we can quickly see how many issues remain unresolved for a particular release, without having to go through them one by one. This makes release planning and progress tracking much more straightforward.

I especially like the idea of a label suggestion tool. Automatically suggesting relevant labels based on issue and PR descriptions could make this workflow even more efficient and consistent, while reducing the manual effort required from maintainers.

Overall, I think this is a practical improvement that could make issue management, collaboration, and release planning significantly more efficient for the Apache Cloudberry community. Thanks for proposing it!

Lirong

[Alena0704]

Thanks for the support, Lirong! It’s helpful to hear how labels have worked in your internal workflow, especially for release planning.
As a first step, I suggest agreeing on the initial set of labels and their intended use. We could then explore options for a label suggestion tool. Are there any existing tools or approaches you’ve used internally that you would recommend?