I've sent off a batch of issues to Rick at GitHub for importing to 
parrot/parrottest2.  This batch should be the same as what's in 
parrot/parrottest but with (most of) the Trac attachments turned into comments 
on issues.  I didn't import any attachments bigger than 80K.  I also took into 
account comments from y'all about the first batch, most notably NOT trying to 
clean up whitespace, which screwed up some patches.

When the new batch is in place, I will check it out, and then I think we'll be 
ready for cutover.

So, the big question I have is: HOW CAN WE TURN TRAC INTO SOMETHING READ-ONLY?

Is there some magic we can do to prevent any new activity on Trac?  I would 
like to get the GitHub issues in place, and then flip a switch, and turn Trac 
read-only.  Who can do this?

xoxo,
Andy

--
Andy Lester => [email protected] => www.petdance.com => AIM:petdance

_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev

Reply via email to