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

[John Arbash Meinel]

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

On 4/8/2011 2:16 PM, Gordon Tyler wrote:
> 
> 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

Except some people only get things via a ppa. And others can only get it
via stable updates, and others can have no trouble downloading trunk and
getting it from there.

So "users" have very different perspectives of "Released".

As such, I don't think you can say one-size-fits all. Rather, just use
"Fix Released" because it is the final step for a bug, and make it clear
what release version(s) the fix is expected to appear in.

I certainly agree with the final decision to use Milestones to track
actual release status.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2fCZIACgkQJdeBCYSNAAOx4ACgjAu2oEPoP15eMj6WgOZo43lj
6W4AoMIeJ6mvWCocImcl7n1FOsCPMAav
=qCI4
-----END PGP SIGNATURE-----