The GitHub migration plan follows. Please let me know if you have any concerns or believe there should be additional points of consideration. Barring objections or glaring omissions, I plan to request assistance from the infrastructure group to put this in place Sunday night beginning at 2100 EDT. God willing it'll be done in under a couple hours.
1. Make source.jasig.org/cas read-only at 2100. 2. Run migration script to create local Git repo. This takes 20-40m and performs the heavy lifting of branch and tag cleanup. The conversion script and related resources are attached to https://wiki.jasig.org/display/CAS/Proposed+migration+from+svn+to+github for review. 3. Create https://github.com/jasig/cas under Jasig organizational account. 4. Clone local repo into local working copy and step inside. 5. Set remote origin to GitHub cas repo and push. 6. Review remote repo for correctness and perform tweaks as needed. (Hopefully there will be none.) 4. Bring source.jasig.org/cas back online rw and replace usual trunk/tags/branches with single README file indicating source now lives at https://github.com/jasig/cas. 5. Switch source.jasig.org/cas back to read-only to emphasize the point. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
