Hi everyone, well that escalated quickly :) Let me share some more background. This is our current definition for the priorities (from https://cwiki.apache.org/confluence/display/FLINK/Flink+Jira+Process).
*Blocker* - infrastructure failures, bugs that block us from releasing *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) need an assignee or an active public discussion otherwise their priority is slowly reduced up to "Not a Priority" automatically by the flink-jira-bot <https://github.com/apache/flink-jira-bot>. The time intervals until they prioritized are configured in https://github.com/apache/flink-jira-bot/blob/master/config.yaml: Blocker: 8 days without assignee or activity Critical 21 days without assignee or activity Major: 67 days without assignee or activity Minor: 187 days without assignee or activity So, the big jump is between Major and Minor, which is why I proposed to set the default to Minor. When you propose new priorities ("Normal") I propose you also share how it would fit in/change this framework, i.e. * What's the definition? * Does it change other definitions? Do we need to migrate tickets? * What would be the Jira Bot configuration? I know, this is a lot to ask, but otherwise I fear we might talk past each other. Cheers, Konstantin On Tue, Jul 27, 2021 at 1:35 PM Martijn Visser <mart...@ververica.com> wrote: > Hi, > > I would introduce a new priority between Major and Minor. I think there's > still value for having a Minor priority, especially for tickets where > something is being reported but there's a workable workaround available. > > With regards to Yun's comment, I think that's a follow-up question on what > to do with tickets that are already in the system that are registered as > "Major". There are currently 4 Blockers, 29 Critical, 938 Major, 2340 Minor > and 0 Not a Priority open tickets. I don't think there's a bulk rule that > can be applied to, for example, move all Major to a Normal state. I do > think this will balance itself out over time if you would introduce > "Normal" as a new default priority and the ones who can change Jira tickets > also check if the right priority is set whenever they work on a ticket. > > Best regards, > > Martijn > > On Tue, 27 Jul 2021 at 12:40, Yun Tang <myas...@live.com> wrote: > > > Hi Konstantin, > > > > How about rename "Major" to "Normal"? We already have higher critical and > > blocker priorities, and I personally usually treat current "major" as > > "normal" priority. > > > > Best, > > Yun Tang > > ________________________________ > > From: Konstantin Knauf <kna...@apache.org> > > Sent: Tuesday, July 27, 2021 18:03 > > To: dev <dev@flink.apache.org> > > Subject: Re: [DISCUSS] Change Default Jira Priority from "Major" to > "Minor" > > > > Quick Question to Martijn, Jingsong: do you propose to rename "Minor" to > > "Normal" or would you like to introduce a new priority between Major and > > Minor? > > > > On Tue, Jul 27, 2021 at 11:44 AM Jingsong Li <jingsongl...@gmail.com> > > wrote: > > > > > I agree with Martijn. > > > > > > My problem is just minor, which will make me a little disappointed. > > > > > > Best, > > > Jingsong > > > > > > > > > On Tue, Jul 27, 2021 at 5:32 PM Martijn Visser <mart...@ververica.com> > > > wrote: > > > > > > > Hi, > > > > > > > > I personally would prefer to use "Normal" as a default priority > > because I > > > > think a lot of people's first reaction is that their reported problem > > is > > > > bigger than a minor loss of function [1], resulting in them choosing > > the > > > > next priority which is currently "Major". > > > > > > > > Best regards, > > > > > > > > Martijn > > > > > > > > [1] > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels > > > > > > > > On Mon, 26 Jul 2021 at 11:54, Caizhi Weng <tsreape...@gmail.com> > > wrote: > > > > > > > > > Hi Konstantin! > > > > > > > > > > Thanks for raising this up. From my point of view it is a > reasonable > > > > > change. But I think it would be better to handle different types of > > > > tickets > > > > > respectively. For example, for bugs a default major seems to be > > better, > > > > > while for others the default shall be minor. > > > > > > > > > > Konstantin Knauf <kna...@apache.org> 于2021年7月26日周一 下午3:35写道： > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > In [1] I proposed to change the default priority of our Jira > > project > > > to > > > > > > "Minor". Most tickets are opened with the default priority. > > Arguably > > > > the > > > > > > majority of these tickets fall into the "Minor" category instead > of > > > > > "Major" > > > > > > according to the definition in [3] (and the implementation of the > > > Jira > > > > > bot > > > > > > [2]). Specifically, tickets in "Minor" stay untouched by the Jira > > bot > > > > > much > > > > > > longer than tickets in "Major". > > > > > > > > > > > > Since this is affecting every new ticket, I would like to > collect a > > > bit > > > > > > more feedback. So, what do you think? > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Konstantin > > > > > > > > > > > > [1] > > https://lists.apache.org/x/list.html?dev@flink.apache.org:lte=1M > > > : > > > > > > [2] https://github.com/apache/flink-jira-bot > > > > > > [3] > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/Flink+Jira+Process#FlinkJiraProcess-TicketsPriorities > > > > > > > > > > > > -- > > > > > > > > > > > > Konstantin Knauf > > > > > > > > > > > > https://twitter.com/snntrable > > > > > > > > > > > > https://github.com/knaufk > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Best, Jingsong Lee > > > > > > > > > -- > > > > Konstantin Knauf > > > > https://twitter.com/snntrable > > > > https://github.com/knaufk > > > -- Konstantin Knauf https://twitter.com/snntrable https://github.com/knaufk
