On Wed, Nov 21, 2007 at 01:44:32PM +0900, James Henstridge wrote:
[adding inkscape-devel back to the CC list]
On 19/11/2007, James Henstridge <james@...1829...> wrote:
On 15/11/2007, James Henstridge <james@...1829...> wrote:
On 15/11/2007, Bryce Harrington <bryce@...961...> wrote:
Hi James,
Hope your flight home wasn't too insane (but I'm guessing it was!) I just wanted to check in with you on the Inkscape import, and see if there's anything more we could do to assist.
I took a few days off after allhands, so only arrived back home this morning. I'll try and get you a new demo import soon. The main tasks are:
- figure out what happened to the rest of the bug reports
- modify the importer to match your status/importance/category usage.
Hi Bryce,
I've updated the demo import of the Inkscape bugs. The missing bugs were due to a faulty download of one SF.net bug report that I did not catch.
I've updated the group, importance and status handling to match your requirements. Please tell me whether it looks okay now.
Hi James,
I did some spot checks, and yes it now looks okay. The bug counts look like they now match up fine, and the bug states look like they've mapped well.
Assuming this import looks okay, what sort of time frame do you want for the migration?
We're now ready to go forward at your convenience.
There are a few timing constraints on our side that need to be taken into account:
- We are rolling out a new version of the Launchpad code base this
week, and I don't think there will be time to complete a migration before that happens. So the earliest will be next week.
Understood.
- The migration process depends on screen scraping SourceForge.net.
If you scrape SF.net too fast, they block your IP address. So it will take a number of hours to get a fresh dump (I won't have to re-download the attachments this time though).
If it is possible to disable filing of new bugs before the migration, that would also be help reduce the chance of lost bug reports.
Certainly. I've looked into this. It is possible to cause the bug tracker (and RFE's, patches) to be "hidden" so people can no longer submit to them. It does not appear to be possible to "lock" them but leave them visible.
Because of this, I think the best approach would be for you to give me an indication of roughly when you'll be able to start the migration. I will then plan on hiding all of SourceForge's trackers for Inkscape and then email you a go-ahead. You can then run the screen scrapers and then bring up the new bug tracking at Launchpad.
Meanwhile, we can let our users know of the downtime, and work on repointing our website bug tracker links to Launchpad. Hopefully then we'll be good to go!
Thanks again! Bryce