On Sun, 17 Aug 2008 13:56:49 -0700 Michael Jennings <[EMAIL PROTECTED]> babbled:
plan: cvs is up - we can lock commit access - but everyone has been informed. devel list, cvs commits list too, and if they commit - they can watch their commits go into a dead black hole. for now it can stay just to service: all devs in the previous cvs "devs" module should have access via the same ssh keys and accounts. there is a devs dir in trunk with all that stuff as before. the auto-cvs-package builders until they move to svn those that are a bit slow on the uptake in grabbing source just in case we screwed something in the svn import. i'd say in a month or 2 - shut it down. but for now it can float idly around. n.b - i have set up full rsync copies of svn and all our www stuff going from e2.enlightenment.org to e1.enlightenment.org (every hour it rsyncs across any changes). as such this means e1 (that currently serves anoncvs) could become the "major" anonsvn server for all the people who use easy_e17 and maybe build packages automatically from svn (as at worst they'd be an hour behind). i can increase the frequency of backups if people want, but 1 per hour seemed enough for now. i also asked onefang to move daily builds to e1 to keep a little load off e2. most web stuff runs off e2 right now and that's probably ok. most of it is very light - except trac. anyway. svn move is mostly done - i have made all the www auto-updater scripts work again. not sure if planet etc. still work. but svn seems to be working (for me). we just need to clean up its contents and dir trees and then get back to business. > This is mostly to solicit raster's plan of action, but other opinions > are always welcome as well. > > Now that we've made the move to Subversion, what is the time frame for > completely shutting down E's CVS? I will keep full backups of the > tree even after deletion, of course, but should access be restricted > at all in the short term? How long should it stick around? > > I can keep it up for awhile just in case, or I can take it down > whenever. We should probably make sure all the docs are updated > first, though. > > What's the plan, Stan? :-) > > Michael > > -- > Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> > Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) > ----------------------------------------------------------------------- > "Et elle m'a dit, 'Tombe, tombe au fond de mon coeur. Les nuits sont > trop longues, et j'ai un peu peur.' Et c'est comme ca qu'elle est > entree dans ma vie, la fille de pluie." -- Roch Voisine > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
