List Archive: gentoo-scm
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Donnie Berkholz <firstname.lastname@example.org>:
> There's 4 main pieces that I can think of offhand:
> 1. Getting a reasonable backend setup that is performant for initial
> checkout, updates, and checkins;
> 2. Figuring out a workflow that makes the most sense, even if it's the
> same one we already have;
> 3. Updating utilities, mainly repoman on the dev side, and rsync
> scripts on the backend; and
> 4. A plan for the actual migration.
> Here's progress so far:
> 1. Working on it
> 2. Draft at <http://dev.gentoo.org/~dberkholz/master_plan.txt>.
> Thoughts? 3. Should be fairly straightforward. Patches welcome!
> 4. Could use some discussion. For example, do we provide
> backwards-compat CVS for a while, or do we just provide a git
> testing server for a while and switch things over all at once?
2. As far as I can tell, this is something we can build upon, though
sorting out details will take some time.
3. What utilities are used by most devs that need to know about the
underlying SCM system? Maybe we can set up a wiki and collect such
things. echangelog and ebump are the only things that come to my mind
instantly. echangelog has Git support, though you should all have a
look at the bugs open against it, and it won't work properly with Git
1.6 as all the git-<command> soft links have been gone. ebump though
has no support for Git at all.
We should really care better for gentoolkit-dev.
4. No backwards-compat, complete switch after some testing time.
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode