Hi,
On Tue, Dec 23, 2014 at 10:31:35PM +0100, Cor Nouws wrote:
One thing that may be handled too: when confirming also check if it
worked before (regression or not) and such.
True. In the end a fully triaged (aka a bug that a QA guys can do nothing more
about and that only can be moved forward
Bjoern Michaelsen wrote on 24-12-14 11:20:
True. In the end a fully triaged (aka a bug that a QA guys can do nothing more
about and that only can be moved forward by a developer) is either:
[...]
And confirming without checking if the bug is in one of the categories
makes working with
Bjoern Michaelsen wrote on 24-12-14 11:20:
and have a list of confirmed bugs that QA can still help about. As such Id
suggest maybe a whiteboard status newfeaturebug for this. Opinions?
Looks good.
Thanks,
Cor
--
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134
Hi Bjoern,
True. In the end a fully triaged (aka a bug that a QA guys can do nothing more
about and that only can be moved forward by a developer) is either:
1/ a regression, which has been bibisected
2/ a non-regression, missing feature (enhancement)
3/ a non-regression, bug introduced
On Wed, Dec 24, 2014 at 12:13:57PM +0100, Robert Großkopf wrote:
Hi Bjoern,
True. In the end a fully triaged (aka a bug that a QA guys can do nothing
more
about and that only can be moved forward by a developer) is either:
1/ a regression, which has been bibisected
2/ a
