← Back to team overview

opencog-dev team mailing list archive

Re: merging work into opencog/main

 

On Thu, Sep 18, 2008 at 2:04 PM, Gustavo Machado Campagnani Gama
<gama@xxxxxxxxxxxxx> wrote:
> Now, just as side joke, here's the *real* reason I have so many dead
> branches on my launchpad workspace: the fabulous people from Canonical
> decided to *remove* the option to delete a branch in Launchpad 2.0 (!!).
> About a month ago I spent at least a couple of hours trying to figure
> out how to do it -- until I gave up. There's probably an obscure and
> undocumented way to do it so, if anyone finds out, please let me know.

1. follow the link for a branch from code.launchpad.net
2. there is a little red negative sign next to the branch
name/description for deletion... assuming you've got permissions to do
so!

> >From the other replies, there seems to be a general consensus that we
> need an unstable branch. So here's a proposal: after I land the 'dynamic
> modules' branch (which is a fairly large patch) and the .deb packages,
> I'll rebase it again against the latest changes from Linas and --
> preferably after others test and review it -- I'll publish it as
> 'unstable' (or whatever you'd like to call it) under the '~opencog-dev'
> workspace.
>
> Then, we merge it back to 'main' whenever people feel that the current
> tree is stable enough. With this model, people have the option of
> branching from main for local experiments and the burden of keeping it
> up to date shouldn't be too large as main won't change so often.
>
> What do y'all think?

Sounds good to me!

J



References