As discussed on foresight-devel, this plan is now underway. On Fri, Sep 03, 2010 at 10:28:02AM -0400, Michael K. Johnson wrote: > I've changed the plan a bit. The remaining plan, in case anyone > is interested in what I'll be doing:
... > * Test email from fdev [DONE] > * Disable all non-mirror accounts on foresight.rpath.org [DONE] > * Wait for mirror to be complete [DONE] > * Reverse direction of mirror [DONE] > * Run mirror [ONGOING] > * Enable commitmail from foresight-commits > * Disable commitmail from foresight.rpath.org > * Enable developer accounts on foresight-commits > * Send instructions on using foresight-commits to foresight-devel > * Set up triggered as well as cron-based syncing for practically > instantaneous public access on main foresight.rpath.org I think that I don't need to trigger it; running it every minute is probably good enough, at least for now. > * Send instructions on how to use fdev and foresight-commits to > foresight-devel > > I'll be trying to keep the amount of time when developers cannot > commit anything to either repository to a minimum... Fixing broken email and removing write permissions on the main repository took longer than I expected. I will try to finish this process this evening. I don't think that there's anything left that is particularly time-consuming, but I need to head home now. :) _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
