Hi Jeremy, Am Mittwoch, 16. Mai 2012, 13:00:04 schrieb Jeremy Whiting: > On Wed, May 16, 2012 at 9:50 AM, Friedrich W. H. Kossebau > > <[email protected]> wrote: > > Those "brave people" are you, Nicolás and Jeremy :) Do you want to pick up > > your work again and be our experts in the kdesdk migration? > > I would love to help out as I am able to. Lots of stuff going on at > home so don't have a ton of time to devote to this, but I would like > to see it happen and can spare a few hours a week to help someone get > up to speed.
Good, thank you! Let's try to spread the tasks on many shoulders where doable, so things take less time for each and the results are quicker seen. > > I myself have not really followed any of the migrations to git, so have no > > real idea about the process. http://techbase.kde.org/Projects/MovetoGit > > only helped me a little. Do kdeedu or kdeutils or else have a log of > > their process which could be followed? > > > > I guess it's something like this: > > > > 1. Decide which repos should be created from which submodules > > 2. Write migration rules > > 3. Setup a test git server with resulting repos to check rules > > 4. Have everyone okay the rules > > 5. Migration! > > a) Put writelock on module in svn > > b) Create real repos by the rules > > c) Configure EBN, API DOX, translations systems (what else?) for new > > repos > > d) Put "Moved to git" note to module in svn > > e) Enable write access to git modules > > > > Correct? > > Yes, that's correct. For 3 we have previously just used scratch repos > in git.kde.org. No need to set up a separate git server. Otherwise, > yes that looks like the process we've used in the past. Okay, so took that as guide to roughly follow for now. Cheers Friedrich _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
