[Bulk] Re: [rfc] Fix committed/released distinction

[Gordon Tyler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
On 4/8/2011 1:06 AM, Martin Pool wrote:
> We do use series tasks for updates to stable series (like 2.2,
> 2.3) and we use the main-project task for fixing something in
> trunk, which is where eg 2.4beta releases come from. We could
> modify things to say that just being landed to trunk counts as fix
> released, whereas for a stable series it is only fixcommitted when
> it's on the branch, and then fixreleased when it's out. Is that
> what you mean?
>

The problem with that is that from a user's perspective, they can't
distinguish between a bug that's been "released" onto trunk or
actually available in a officially released version. "Fix Released"
should be treated as "a user can download the latest officially
released tarball/installer and get this fix".

Ciao,
Gordon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iQEcBAEBAgAGBQJNnvyYAAoJEIrPJfWinA2uUnUH/2GABnKjpJBT72sIghpEyasS
u+d2BcUhmEh+f4v3KKmF+PQrwCCUwBSuvBvz/5gvjCfW9+q2cvUhBoxMU45UNHPv
o++p1sL7oaV0eNNIQF9h8u21twEbYotQy0LaATlslJuV8j7Es6WHcFtpxUiKrB83
D63ZGKXUaMF8s5bc9lgQPJ0AiTWch1lv8vS2t9oHsagwryMOvgNxWWRbNGR3R7k3
vLyZArrxu79Pk2ifU88n8u7BiyFWiO2EZBEBXT+wbckU/GvNc9UrcYv+NR4Dqhtb
9Z0aUsh7DnlLs9nGigorw+z30ZOLo18sB9rKXegJUVtSI2TFQGNq+hRHi96BL7A=
=MdCg
-----END PGP SIGNATURE-----