1 |
Donnie Berkholz <dberkholz@g.o>: |
2 |
> There's 4 main pieces that I can think of offhand: |
3 |
> |
4 |
> 1. Getting a reasonable backend setup that is performant for initial |
5 |
> checkout, updates, and checkins; |
6 |
> 2. Figuring out a workflow that makes the most sense, even if it's the |
7 |
> same one we already have; |
8 |
> 3. Updating utilities, mainly repoman on the dev side, and rsync |
9 |
> scripts on the backend; and |
10 |
> 4. A plan for the actual migration. |
11 |
> |
12 |
> Here's progress so far: |
13 |
> |
14 |
> 1. Working on it |
15 |
> 2. Draft at <http://dev.gentoo.org/~dberkholz/master_plan.txt>. |
16 |
> Thoughts? 3. Should be fairly straightforward. Patches welcome! |
17 |
> 4. Could use some discussion. For example, do we provide |
18 |
> backwards-compat CVS for a while, or do we just provide a git |
19 |
> testing server for a while and switch things over all at once? |
20 |
|
21 |
2. As far as I can tell, this is something we can build upon, though |
22 |
sorting out details will take some time. |
23 |
3. What utilities are used by most devs that need to know about the |
24 |
underlying SCM system? Maybe we can set up a wiki and collect such |
25 |
things. echangelog and ebump are the only things that come to my mind |
26 |
instantly. echangelog has Git support, though you should all have a |
27 |
look at the bugs open against it, and it won't work properly with Git |
28 |
1.6 as all the git-<command> soft links have been gone. ebump though |
29 |
has no support for Git at all. |
30 |
We should really care better for gentoolkit-dev. |
31 |
4. No backwards-compat, complete switch after some testing time. |
32 |
|
33 |
V-Li |
34 |
|
35 |
|
36 |
-- |
37 |
Christian Faulhammer, Gentoo Lisp project |
38 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
39 |
|
40 |
<URL:http://www.faulhammer.org/> |