Hello Beam community, I was thinking about this and found some information to share/discuss. Would it be possible to confirm my thinking on this:
- There are 5 priorities in the JIRA system today (tooltip link <https://issues.apache.org/jira/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels> ): - - *Blocker* Blocks development and/or testing work, production could not run - *Critical* Crashes, loss of data, severe memory leak. - *Major* Major loss of function. - *Minor* Minor loss of function, or other problem where easy workaround is present. - *Trivial* Cosmetic problem like misspelt words or misaligned text. - How should JIRA issues be prioritized for pre/post commit test failures? - I think *Blocker* - What about the flakey failures? - *Blocker* as well? - How should non test issues be prioritized? (E.g. feature to implement or bugs not regularly breaking tests). - I suggest *Minor*, but its not clear how to distinguish between these. Below is my thinking: But I wanted to know what the Apache/Beam community generally thinks about these priorities. - *Blocker*: Expect to be paged. Production systems are down. - *Critical*: Expect to be contacted by email or a bot to fix this. - *Major*: Some loss of function in the repository, can issues that need to be addressed soon are here. - *Minor*: Most issues will be here, important issues within this will get picked up and completed. FRs, bugs. - *Trivial*: Unlikely to be implemented, far too many issues in this category. FRs, bugs. Thanks for helping to clear this up Alex
