lp:launchpad/devel doesn't show up in web form for proposing merges

[Robert Collins]

e.g.
https://code.edge.launchpad.net/~lifeless/launchpad/merge/+register-merge

only lists lp:launchpad

 affects launchpad-code
 done

[Tim Penhey (thumper)]

It will once you have done it once if that is any help.

[Tim Penhey (thumper)]

We really should have a way to identify branches that should show up by default (ideally with helper text).

[Jonathan Lange (jml)]

I don't think we should do anything to fix this bug. We strongly encourage merges to trunk and already have pretty good support in place for projects with many "trunks" – at least on this form.

[Robert Collins (lifeless)]

So jml, are you saying that launchpad/devel isn't a trunk?

[Jonathan Lange (jml)]

On Mon, May 31, 2010 at 10:36 PM, Robert Collins
<email address hidden> wrote:
> So jml, are you saying that launchpad/devel isn't a trunk?

It's a trunk, but not in a way that Launchpad recognizes, or even
should recognize. It should not show up by default. The "multiple
trunks" thing is something that Launchpad already has enough support
for. e.g. once you've proposed a merge against it, it shows up anyway.

[Robert Collins (lifeless)]

I think I'm irrevocably confused about this then. Perhaps I should rephrase.

'the place that launchpad developers should propose merges against
doesn't show up in the web for for proposing merges unless something
undiscoverable is done which fixes it for that user'

[Martin Pool (mbp)]

On 2 June 2010 09:08, Robert Collins <email address hidden> wrote:
> I think I'm irrevocably confused about this then. Perhaps I should
> rephrase.
>
> 'the place that launchpad developers should propose merges against
> doesn't show up in the web for for proposing merges unless something
> undiscoverable is done which fixes it for that user'

Tim's comment #2 agrees with this as I see it.

There are two problems here:

1- This form is almost unique in Launchpad in that it populates itself
with values that you personally have used previously; that's quite a
good pattern in some ways but it's confusing because it's so
inconsistent. (I would love if Launchpad did this for People too; I
commonly assign or subscribe the same people.) I think there's a
separate bug for that.

2- The default population is poor.

Suggesting the most commonly proposed targets across all MPs might be better.

--
Martin <http://launchpad.net/~mbp/>