Tasks #10455
closedImprovements to the tracker - suggestion
0%
Description
In the context of "nightlies" (altho it may benefit our community and downstream development as well) - it seems that the tracker is not fine tuned to help us effectively find a set of issues as they relate or were found in particular branch/release and cross reference against suites, that actually (with failed jobs) they were found in.
Please consider customizing the tracker to have:
1. Drop-down that would list our branches, e.g. "master", "next", "giant" (+ "official releases maybe?)
2. Drop-down that would list our ceph-qa suites (this should replace the current open text field "Suite")
Those items can be added as mandatory if desired.
Pls add your comments for the tracker improvements.
Updated by Sage Weil over 9 years ago
1. we could put stable branch (firefly, giant, etc) vs master. the master vs next changes so often I'm not sure its worth putting that in. what might be more accurate is the sha1 but those are less helpful to humans.
2. i assume this is so that we can quickly do a search to see which bugs affect which test suites? there will be lots of cases where a bug affects lots of tests suites and it won't really help. but if it will improve the workflow i'm not sure it can hurt..
Updated by Yuri Weinstein over 9 years ago
re: #2 - yes that's correct, it will also help us at the end of major releases (and minor as well) to make assessment of readiness (aka our matrix list)