Process questions

[John Arbash Meinel]

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


...

>>    Is it OK for a very-occasional contributor like me to mark
>>    bugs like this -- even ones I've had no previous involvement
>>    with -- as "Fix Released", or should I bring them to the
>>    team's attention so someone more official can decide?  If the
>>    latter, is there a less obtrusive way than email to this list?
> 
> Editing anything that launchpad lets you edit is fair game. It can be
> helpful to include a comment at the same time (like, "Confirmed that
> this is resolved in 2.3.0" or similar) to make the intention clear.
> 
> Martin
> 
> 

I would caution that changing a bug state should always be accompanied
by context. "This was fixed in XX,YY" is sufficient. Otherwise we have
to manually go back and confirm everything that is done. Similarly,
changing the state from Fixed to Confirmed is ok, but only if you've
actually validated it, and give us feedback to that effect.

We *love* to have people gardening our bug tracker, but if you don't
provide the context, then it makes it hard for us to trust that the
changes are accurate.

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

iEYEARECAAYFAk1RtJ0ACgkQJdeBCYSNAAOIAgCgqFods4hmDaUW71ugXmD/tDmU
HnQAoJuKkN+wzQ0inaCSUPwv4ganVNt/
=8eJA
-----END PGP SIGNATURE-----