[wildfly-dev] Re: 'Critical' JIRA cleanup

We've got a lot ofJIRAs with 'Critical' priority that have been inactive for a long time. I think we should define 'Critical' as roughly "important enough that we need to work on it soon." At some point if something goes unaddressed long enough that's a sign that it's not important enough to be called critical. I propose doing the following: for any Critical WFLY or WFCORE that was opened > 12 months ago and hasn't shown signs of activity since the WF 32 release, I'll leave a comment saying I plan to downgrade it to Major unless the assignee says they plan to deal with it for the WF 34 cycle. And then a couple weeks later downgrade issues. Similarly, for issues with Fix Version 33.0.0.Final that have been rolling from release to release since WF 31 or earlier, when I release 33 I intend to remove the Fix Version instead of rolling it to 34. WDYT?

-- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His _______________________________________________ wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org Privacy Statement: https://www.redhat.com/en/about/privacy-policy List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...