THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
The following page is based on a discussion in May 2020 and more importantly another discussion in March 2021, the community agreed on the following definitions for the fields in the FLINK Jira project.
| Table of Contents |
|---|
Goals
- clearer communication and expectation management with the community
- a user or contributor should be able to judge the urgency of a ticket by its priority
- if a ticket is assigned to someone the expectation that someone is working on it should hold
- generally reduce noise in Jira
- reduce overhead of committers to ask about status updates of contributions or bug reports
- “Are you still working on this?”
- “Are you still interested in this?”
- “Does this still happen on Flink 1.x?”
- “Are you still experiencing this issue?”
- “What is the status of the implementation”?
- while still encouraging users to add new tickets and to leave feedback about existing tickets
...
Critical - test instabilities, security related issues, important components is non-functional for important use case
Major (default) - typical feature requests, bug that affects some use cases
Minor - nice to have feature requests, wishes, not necessarily under active development or discussion, catch all
Not a Priority - stale feature request or bug report
Tickets (except Not a Priority) Tickets Major and above need an assignee or an active public discussion otherwise their priority is slowly reduced up to "MinorNot a Priority" automatically by the the flink-jira-bot.Minor Tickets without an update for a long time (180 days) are closed automatically by the flink-jira-bot.
| Info | ||
|---|---|---|
| ||
Only Bugs can be Blocker/Critical. |
...
As a rule, we Close tickets instead of Resolving them when they are done.
Background: There are semantic differences for Resolve and Close (implementor vs reporter considers it done), but I don't see how they practically apply to the Flink project. Looking at the numbers, Flink has 11066 closed tickets, and 3372 resolved tickets (that's why I propose to close instead of resolve)
Labels
| Label | Description | ||
|---|---|---|---|
| test-stabilitytest instabilities | Test stability issues that cause our CI to fail. | ||
| starter | tickets suitable for new contributors | Jira issues that can be picked up by contributors that are not necessarily familiar with Flink-internals, yet, but want to contribute. | |
| usability | Labels Jira issues that cover improvements in usability of Flink | ||
| release-testing | Labels Jira issues that are created as part of the release testing phase at the end of a Major/Minor release cycle | usability | usability issues |
stale-blocker | A Blocker ticket without an assignee or public discussion. It is about to become "auto-deprioritized-blocker" by the flink-jira-bot. | ||
stale-critical | A Critical ticket without an assignee or public discussion. It is about to become "auto-deprioritized-critical" by the flink-jira-bot. | ||
stale-major | A Major ticket without an assignee or public discussion. It is about to become "auto-deprioritized-major" by the flink-jira-bot. | ||
stale-minor | A Minor ticket without an assignee or public discussion. It is about to become "auto-deprioritized-minor" by the flink-jira-bot. | ||
auto-deprioritized-blocker | A Blocker ticket that has automatically been moved to Critical by the flink-jira-bot. | ||
auto-deprioritized-critical | A Critical ticket that has automatically been moved to Major by the flink-jira-bot. | ||
auto-deprioritized-major | A Major ticket that has automatically been moved to Minor by the flink-jira-bot. | ||
auto-closed | A Minor ticket that has automatically been closed by the flink-jira-bot. | ||
stale-assigned | A Major+ ticket that is assigned but has not received an update for some time. It is about to become "auto-unassigned" by the flink-jira-bot. | ||
| Auto-unassigned | A Major+ ticket that has been automatically unassigned by the flink-jira-bot. |
Release Note
| Status | ||||
|---|---|---|---|---|
|
...