launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-02-14 05:20 PM, Ian Booth wrote:
> One issue for me is that the
> https://dev.launchpad.net/QAProcessContinuousRollouts page lists qa-ok
> as meaning:
> 
> qa-ok: The branch is verified and implements successfully what it proposes.
> 
> which is very different to "this branch is deployable from a RM
> perspective but may not actually fix what it says it does".

To me, the "Fix verified" meaning belongs between "Fix committed" and
"Fix released" in the bug status list.

> So there's
> really two different concerns here - the QA perspective and the RM
> perspective - and the one tag (qa-ok) is perhaps being used for both.

Right, but I did ask Robert which one was primary and he said the RM
perspective one was.

> - there should be process automation (say using qa tagger) to update a
> bug's status (if required) in response to a qa tag being applied

Once qa tags are orthagonal to the bug fix status, that should not be
necessary.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1bUQEACgkQ0F+nu1YWqI0A6gCghwq1oyfBaw/IsijV//N/+ktA
unAAnizD5+Q1M3S8B7H3bQUDRlujycRQ
=rax2
-----END PGP SIGNATURE-----