Process questions

[Martin (gzlist)]

On 08/02/2011, Eric Siegerman <lists08-bzr at davor.org> wrote:
>
> 1. I discovered a small bug, and have a fix ready for review.  Is
>    it preferred that I create a bug report and tie the MP to it,
>    or just submit the MP on its own?

I like having bugs personally, it means the problem doesn't get lost
if it turned out I bit off more than I could chew. If it's not a
problem but just a trivial edit I just throw up a merge proposal.

> 2. Another change I'm working on isn't yet ready for review,
>    because I need help writing tests.  Should I create an MP for
>    it anyway to put it on the Patch Pilot's work queue, or is it
>    better to ask here or on IRC?

An mp is a good way of making sure people see the code, and isn't hard
for the patch pilot to handle. However, you might get better feedback
if you can corner someone on IRC.

>    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