On Thu, Feb 23, 2006 at 12:16:10PM -0500, Vivek Khera wrote: > > On Feb 23, 2006, at 10:49 AM, Chris Browne wrote: > > > There may be other things I'm not thinking of; that's why this is a > > Request For Comments :-). > > Well, is moving to svn such a critical thing? It seems that unless > we're doing many branches and many vendor drops and such, cvs is > sufficient for now. > > The mailing lists could move at any time. It would probably be a > good opportunity to get rid of the cruft on the list by having > everyone re-subscribe. No matter how good a mailing list manager is, > there are always dead addresses that accumulate after a while... If > we could arrange it that every existing member got an invitation to > just click a link that would be ideal.
I disagree. First, if there are invalid emails subscribed, who cares? Second, by creating new lists, you'd lose the archives of everything that's been discussed, which seems like it would be a huge loss. > Moving over the history of the bug tracker DB is important. We don't > want to lose any institutional memory. /me wonders if it could be > scripted with WWW::Mechanize.... I believe that a script to do that exists. I've been pushing for the creation of a project on pgfoundry for the migration, so that stuff can get posted and people can help. If there is such a script then I suspect we might actually be close to being able to seamlessly migrate projects. There shouldn't be any issue with moving mailing lists, SVN exists (and worst-case a seperate install of viewcvs could be setup until there's native gforge support for SVN), and I believe everything else is in the database. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
