GitHub Issue Labels

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: github issue labels

| username: TiDBer_qJQrqnS9

I would like to ask, in the GitHub TiDB issue, what label assigned by the developers would indicate that my bug report is indeed recognized as a TiDB bug?

| username: hey-hoho | Original post link

Blind guess.

| username: TiDBer_XvaWxzWs | Original post link

This label is added by the developer/user who submitted the bug. I would like to ask, apart from this label, does assigning any other label mean that the bug has been confirmed?

| username: hey-hoho | Original post link

It is not necessarily written by the issue submitter themselves; it mainly depends on whether the person is a project committer, reviewer, or other management roles. Different labels have different meanings, which can be understood from their literal meanings.

| username: TiDBer_XvaWxzWs | Original post link

May I ask what the sig/execution label means?

| username: hey-hoho | Original post link

Blind guess.

SIG refers to Special Interest Groups, and execution means this issue belongs to the TiDB executor module. Not sure if that’s correct…

I’ll tag the development expert @tiancaiamao to take a look :eyes:

| username: TiDBer_XvaWxzWs | Original post link

Thank you :blush:

| username: TiDBer_a0wVPNxf | Original post link

First, a Member or developer will reply to you. Based on their response, you can determine whether the bug needs improvement or if it exists due to the design of the architecture itself, and currently, there is no effective solution for improvement.