launchpad-dev team mailing list archive

[Deryck Hodge <deryck.hodge@xxxxxxxxxxxxx>]

On Wed, Sep 29, 2010 at 7:05 AM, Deryck Hodge
<deryck.hodge@xxxxxxxxxxxxx> wrote:
> On Wed, Sep 29, 2010 at 6:50 AM, Jonathan Lange <jml@xxxxxxxxxxxxx> wrote:
>> I'm practically an old hand and they're the same problems for me.
>>
>> There are a few tricks you can use to not forget branches:
>>  * Consult https://code.edge.launchpad.net/~jcsackett/launchpad
>>  * Consult https://code.edge.launchpad.net/~jcsackett/+activereviews
>>  * Delete local copies (or checkouts) of branches after they've been
>> merged into stable/db-stable
>>  * Keep the number of branches low
>>
>> I especially rely on the third one, since it's really easy for me to
>> do `ls ~/src/launchpad` to see what work I've got outstanding.
>
> The kanban board should help with the last item.  We're making sure
> cards correspond to branches rather than bugs on the bugs team board.
> Part of this is to better reflect the work we're doing and see if that
> helps cycle time and part of it is to make sure we don't have work
> lingering forever.
>

As I clicked send, I realized this doesn't help non-Canonical
Launchpad devs.  But those of us using the Kanban board can add a card
for community dev branches when we land those on another dev's behalf.

Cheers,
deryck