On Fri, Dec 2, 2011 at 7:03 AM, Eric S. Raymond <[email protected]> wrote: > Arnaud Quette <[email protected]>: >> > Maybe not that long. But I'll know better in a day or two. >> >> perfect, I was more thinking about weeks or so. > > Actually, now that I have svnsync working it shrinks the window more. > It means I can do things in this sequence: > > 1. sync the nut repo, > > 2. do all the difficult conversion stuff - comment editing, reference lifting. > > 3. save the results, which are basically a huge comments file in mailbox form > and a map from Subversion commit IDs to stream marks. > > 4. Pass it to Charles to review > > 5. He either decides it's ready and we deliver, in which case I'm done, or > > 6. I incrementally resync the repo > > 7. I do the difficult stuff on the handful of new commits, > > 8. Jump back to step 3. > > Result: No commit freeze at any point until we're ready to install the git > repo for production. Which, with correct preparation, will take on the order > of half an hour - with that time being dominated by the time reqired to > upload the git repo to its public location.
Eric, On the NUT timescale, half an hour isn't long at all for a code freeze. I haven't played with Alioth's git support so I don't know what their equivalent is for "rm -rf repository". But I'm partial to Github over Alioth anyway - especially now that they have the concept of both user repositories and project repositories, and they support non-fast-forward updates by default. Do you have a Github account? Or is there another hosting service that you would recommend? (With Git being as flexible as it is, I don't have a problem with staging the conversion somewhere else if that makes things easier, and pushing the completed tree over.) -- - Charles Lepple _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
