Thorsten Ziehm wrote: > Hi QA community, > > last week the automated testing team identified 2 regressions, which > brought up more than 500 crashes at the test runs on the last master > builds [1]. This leads to a hold of building the next master, until > these regressions were fixed. The issues were filed with priority 1. I > thought this handling was covered by the guidelines for issue handling > [2]. But I was wrong. Currently it isn't defined in the guidelines, > that an issues which hinder automated testing significantly can be set > to priority one. > > If I do not get any negative feedback in the next week, I let insert > the following part in the guidelines for priority 1 issues : > "Issue which hinders automated testing significantly" > +1
James McKenzie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
