Bug tracker import for sbnc

Hi Gunnar,

The bug export looks mostly good to go. A few bugs have a problem
which you might like to look into.

Bugs 77, 106, and 111 have attachments with no contents, for example:

      <attachment>
        <mimetype>application/zip</mimetype>
        <title/>
        <filename>sbnc.zip</filename>
        <type>UNSPECIFIED</type>
--> <contents/>
      </attachment>

Note that the <contents> tag should contain base64 encoded data
(xsd:base64Binary is how it's defined in the schema).

I will file a bug to improve the bug-export.rnc schema definition to
ensure that this kind of problem is detected earlier.

Gavin.

Hi Gavin,

thanks for noticing that. Apparently the MantisBT->Trac import script I used didn't work properly; instead it 'imported' all my attachments as empty files which were then turned into those empty <contents> tags by the Trac->Launchpad importer.

I've uploaded a new version at http://gunnar.shroudbox.net/sbnc_mantis_bugs_v2.xml

Best regards,
Gunnar Beutner

sbnc_mantis_bugs_v2.xml imports cleanly into a local instance of Launchpad. I'll request an import into a staging environment now so that you can take a look.

sbnc_mantis_bugs_v2.xml has imported cleanly into qastaging. If you
update shroudbnc to use Launchpad for bugs at:

  https://bugs.qastaging.launchpad.net/shroudbnc/+configure-bugtracker

you can take a look through them. Let me know if you notice any
problems.

If they're okay, would you like me to get sbnc_mantis_bugs_v2.xml
imported into production? Some people choose to freeze their bug
tracker first, then send over another export at a mutually agreed time
for a quick switch over.

Gavin.

Hi Gavin,

thanks so far. We've found a few issues with our last XML dump:

* All NEW issues were assigned to an 'anonymous' user
* Some of our users weren't properly mapped to existing LP users

These problems should be fixed in our latest XML dump: http://gunnar.shroudbox.net/sbnc_mantis_bugs_v3.xml - Could you please do another test import with that new XML dump?

As for the import into the production system: When would be a good time for you? We can probably disable our existing bug tracker on sf.net for an extended period of time (e.g. 24 hours).

Best regards,
Gunnar Beutner

119 bugs imported without error into qastaging. You can see them in a
new project here:

  https://bugs.qastaging.launchpad.net/shroudbnc2

They have different bug nicknames to the ones specified in your bug
data because they have to be unique, and we've already imported this
set of bugs before into the same database. The import into production
will use the correct nicknames.

> When would be a good time for you?

I work Monday to Friday between 0900 and about 1800 UTC. I am not
available on Thursday 17th and Friday 18th. Pick a time :)

Hi Gavin,

I just noticed that you are cc'ed on all bugs on the new shroudbnc2 bug tracker, which might be a nuisance for you if this is carried over into the production system.

-Christoph

That's because I registered the shroudbnc2 project, and didn't specify
a bug supervisor; the owner gets automatically CC'ed instead. Thanks
for the concern though :)

Hi Gavin,

the latest XML dump seems fine. Can't seem to find any more problems. :)

As for the final import... how about tomorrow at around 12:00 UTC? Or if that's too short notice maybe next monday.

Best regards,
Gunnar Beutner

Brilliant. 1200 UTC tomorrow is good.

Ok, cool, an up-to-date XML dump will be at http://gunnar.shroudbox.net/sbnc_mantis_bugs_v4.xml :)

All done without error.

You'll need to update the bug tracker to be Launchpad at:

 https://bugs.launchpad.net/shroudbnc/+configure-bugtracker

Nickname redirections are working, for example:

  https://bugs.launchpad.net/bugs/sbnc-1

redirects to:

  https://bugs.launchpad.net/shroudbnc/+bug/716972

Let me know if you have any problems.

Gavin.

Hi Gavin,

thanks a lot. :)

Best regards,
Gunnar Beutner