Jeroen T. Vermeulen wrote:
> Once this is implemented, we can track Q/A through bugs: you land a
> branch to fix bug X, and bug X automatically gets tagged as needing Q/A.
> The tags make it easy to view Q/A workload for persons, teams,
> categories, etc.
>
> In the Translations team we've been working this way for a few months
> and it works very nicely—except this bug is the missing link for the
> scripts to figure out the right bug based on a commit.
We already automatically link branches to bugs based on a commit. Why
do you need something else?
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeroen T. Vermeulen wrote:
> Once this is implemented, we can track Q/A through bugs: you land a
> branch to fix bug X, and bug X automatically gets tagged as needing Q/A.
> The tags make it easy to view Q/A workload for persons, teams,
> categories, etc.
>
> In the Translations team we've been working this way for a few months
> and it works very nicely—except this bug is the missing link for the
> scripts to figure out the right bug based on a commit.
We already automatically link branches to bugs based on a commit. Why
do you need something else?
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkt oUfkACgkQ0F+ nu1YWqI1duwCfQV WdzUJQAu8/ cjcbRPrdC2+ I T3rMJxB+ i2xDQ2cfO
oVkAn2vADeBZu1O
=5UiM
-----END PGP SIGNATURE-----