opencog-dev team mailing list archive

[Gustavo Machado Campagnani Gama <gama@xxxxxxxxxxxxx>]

Hi David,

On Wed, 2008-05-21 at 18:58 +1000, David Hart wrote:

> The import and changes are great, thanks! The staged migration is a
> good idea. When we're satisfied that everything is correct, and the
> launchpad/bzr bug is fixed, first-time checkouts should be as simple
> as
> 
> bzr branch lp:opencog
> 
> which I expect means moving
> bazaar.launchpad.net/~opencog-dev/opencog-framework/main to lp:opencog
> (the same as bazaar.launchpad.net/opencog ; I'll ask how this can be
> done server-side, when the time comes).

According to
http://news.launchpad.net/general/the-great-source-code-supermarket
you'd have to set the "opencog-framework/main" branch as the "default
branch" of project opencog.

I couldn't find any options in Launchpad's UI to do it, so I'm
_guessing_ that this option will only be available to the the project's
owner/maintainer (i.e., you David :-)).

Anyway, the shortcut "lp:~opencog-dev/opencog-framework/main" currently
works (but it's read-only, I think):

$ bzr checkout lp:~opencog-dev/opencog-framework/main

> The launchpad/bzr bug from svn-import sucks. I think we can live with
> it for the few GSoC students who will use the public repository, since
> the workaround is only needed on the first checkout.

Right. In any case, now that we have bzr I think we should discourage
the "checkout + hack + commit" workflow. In my opinion, it's best to use
either "branch + hack/reverse/rebase/commit + push" or "branch +
hack/reverse/rebase/commit + bind + commit + unbind".

(I think everybody in this list is familiar with these concepts, but if
that's not the case, have a look at
http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#team-collaboration-central-style).


--
Gustavo