launchpad bug tracking?

[Dougie Richardson]

If you are working on it then you need to let others know, by
assigning the bug to yourself (usually) otherwise others will work on
it, as happened here.

If it was me, I'd review the patch and decide whether or not to include it.

That said, it isn't a documentation team package and they may work
totally differently - judging by the first comment its simply a case
of submitting patches - if I was you I'd let them know that you're
working on this.

Regards,

Dougie Richardson
http://www.lynxworks.eu/
dougierichardson at ubuntu.com



2009/3/15 Ekaterina G. Potapova <egeomar at mail.ru>:
> Hi all,
> Help me please to understand how launchpad works. I have at the moment
> the following problem. I'm working on the Rhythmbox manual and I am
> subscribed on the bag concerning the Rhythmbox manual
> (https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/329389). Today
> somebody added on the launchpad his patch - a piece of documentation
> describing this RB feature. Tell me please what happens next to this
> patch? Does somebody include the patch into the manual? As for me I
> appreciate the facts in this patch, but I didn't like the style, and I
> think this abstract needs to be rewritten. So what is better - to ignore
> the patch at all and to write this section from the very beginning, to
>  contact the  author of this patch and discuss new version of the
> patch, to post my comments on this on the  launchpad? What do you
> usually do in such occasions?
> Thanks,
> Katya Potapova
>
>
> --
> ubuntu-doc mailing list
> ubuntu-doc at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc
>