On Tue, Oct 16, 2012 at 5:54 PM, Nathaniel Smith
On Tue, Oct 16, 2012 at 9:06 PM, Thouis (Ray) Jones
wrote: On Sun, Oct 7, 2012 at 10:15 AM, Thouis (Ray) Jones
wrote: I plan to import all the Trac issues to github by the end of this week. I want to get an up-to-date snapshot of the Trac DB, and run another test import with it (just to make sure there's nothing in recent bugs that isn't handled).
Previous test imports here: https://github.com/thouis/numpy-trac-migration/issues
I successfully imported all the issues from a more recent snapshot to the test repository as @numpy-gitbot, rather than @thouis (to save myself from getting pulled into every bug's discussion).
If no one sees any problems with the latest imports (basically, the last 2000 or so by github issue #) , I think it's ready for the real transfer to the numpy github repository.
This is really fabulous; thanks for all the effort you've put in!
But... I am quite concerned that we're still linking to attachments in the trac, e.g.: https://github.com/thouis/numpy-trac-migration/issues/6002#issuecomment-9492...
This means that we can't ever take down the trac without breaking all our github issues; we're committing to keeping the trac running indefinitely. Doesn't that kind of defeat a lot of the point...?
Not actually. I have a snapshot of the attachments, as well, and once there's a place for them live (another repository, possibly), we can use the github API to edit the issues in place to point to the new URLs. Ray