On Wednesday 07 October 2009, Zach Welch wrote: > > > I've got a patch to do most of that. How about this process: > > > > - At time Z, commit a patch to SVN to make builds emit > > a warning "current repository is <URL>" ... so that > > the archival SVN history isn't trashed. > > > > - Also at time Z, and after syncing to the version right > > before that "disable" patch, commit a patch to GIT which > > makes the GIT tree reference GIT not SVN. > > > > - At time Z+1, both patches are upstream. Now it's safe > > to make the SVN repository read-only. > > > > - Beginning at time Z+2, nobody uses SVN any more. Send > > an email to the list finalizing that switch. > > > > I can handle the two commits, but can't make SVN read-only. > > Zach, will you take care of that, and sending the announce? > > > > Where "Z" is about 5pm PST today, and values of "1" and "2" > > are convenient for whoever handles those last two points. :) > > These sound like great ideas. I can execute my part of this plan, yes.
OK, we're effectively at time Z+2 ... except for making SVN be read-only. Turns out that we can't yet disable writes to that, so we don't yet have protection against lazy maintainers. :) - Dave > > > - Copy all existing File Releases to SF.net. > > > - Update project summary information on both sites. > > > - Post an announcement that describe the changes. > > > > Yes. Copying the file releases can be done at any time, > > as can most of the project summary info updates. IMO, do > > them soon after finishing the GIT switch. > > Ack. I will take care of this too. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
