launchpad-dev team mailing list archive

[Jonathan Lange <jml@xxxxxxxxxxxxx>]

On Fri, Nov 19, 2010 at 12:57 PM, Danilo Šegan <danilo@xxxxxxxxxxxxx> wrote:
> У пет, 19. 11 2010. у 09:51 +0000, Jonathan Lange пише:
>>
>> FWIW, when we initially migrated to Launchpad for codehosting, we made
>> devel the development focus (i.e. lp:launchpad), but we changed it to
>> db-devel after folk complained about the inefficient uploads of
>> db-devel based branches. (Launchpad sets the default stacked-on branch
>> to the development focus.)
>
> Is this not still the issue?  db-devel is always going to be a superset
> of devel.  Or, is the assumption that we'll have fewer and fewer
> landings on db-devel directly for this to be an issue?
>

It's an issue. With our current branch set up, we'll always be facing
a trade-off.

Note that:
  * stacking on devel is not wrong, it is simply slower; proposing to merge to
    db-devel is wrong

  * you can specify the stacked-on branch when pushing; the default is
just that.

  * we could also fix the underlying issue by providing a way for a
project to configure
    its default stacked-on branch separately to the dev focus. I had
this in the back
    of my head when I first added stacking support, so it wouldn't be
*that* hard to do.
    Launchpad is probably the only project that would want such a thing.

> How do we do an experiment along these lines?
>

Change the development focus to devel. See what breaks and who complains.

jml