On Mon, Jul 10, 2017 at 01:58:10PM -0700, Adam Williamson wrote: > > It seems like it would be useful if we could have a way to connect "I'm > > making an update in bodhi!" back to "This update is likely to affect > > a given release criteria". For example, it would be nice to have > > something show up in bodhi noting that updates to Firefox might affect > > https://fedoraproject.org/wiki/QA:Testcase_desktop_browser > > We can already link packages and test cases such that updates that > include those packages will always list those test cases: Yes. This is cool. > https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation > I believe there's possibly some kind of bug with the process of syncing > the wiki categories into Bodhi at present, I'm not totally sure of the > current status of that, but the mechanism is already there. Also I have a request to make a drop-in-files thing which I hope will be easier for packagers than dealing with wiki categories, which seems to be a barrier. > > and even better, if that would also show up for updates to Firefox's > > dependencies. > This isn't done yet. (And honestly, doing it in a simple-minded way > would be a bit tricky; do we really want, say, every update to glibc > listing pretty much every package-linked test case that exists?) No. :) I don't really mean test cases; I mean release criteria and I just followed links too far when making an example above. > There really wouldn't be any 'tension' in adding the browser test case > to the firefox package categories, so we could just go ahead and do > that. Establishing links to *release criteria* - which is what you keep > saying, but then your example involves a test case and not a release > criterion, which confuses me a bit - is harder, because we don't really > have any representation of the release criteria which is easy to > interact with programmatically... More wiki categories? :) -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
