locations.conf ideas?

[Martin Pool]

2009/7/4 Jonathan Lange <jml at mumak.net>:
> Hello all,
>
> I've just been helping someone get set up for Bazaar development. We
> got over the shared repository hurdle pretty easily, but soon we hit
> the "submit a patch" hurdle.
>
> To make everything work nicely, we ended up manually editing
> locations.conf to look an awful lot like this:
>
> [/home/jml/src/bzr]
> submit_branch = /home/jml/src/bzr/bzr.dev
> public_branch = lp:~jml/bzr
> public_branch:policy = appendpath
> push_location = lp:~jml/bzr
> push_location:policy = appendpath
> submit_to = bazaar at lists.canonical.com
>
> [/home/jml/src/bzr/trunk]
> public_branch = lp:bzr
>
> Is there something we could have done that would have been simpler
> than that? If not, what can we do to make it simpler?

I think that is the best way to set it up at present.  However for
3.0, once this format is out, I think we need to look at higher-level
ways to express what's going on here:

"For the project bzr"
"I work on it in /home/jml/src/bzr"
"It's hosted on Launchpad"
"I push my branches to Launchpad"
"I'm jml on Launchpad"
"You can propose reviews by sending mail to bazaar@"

I'm not suggesting we should directly add configuration items for all
of these statements but it is useful to untangle them.  Some of them
have different scopes: you're probably(*) known as jml for all your
interactions with Launchpad; it's true for everyone that bzr is on
Launchpad and uses that list, but not true that everyone would publish
their personal branches there.

See <http://doc.bazaar-vcs.org/devnotes/bzr-2009-ui-refresh.html> and
very many previous threads.

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