[Zope-dev] Moving the Zope 2 bugtracker to Launchpad
lists at zopyx.com
Tue Aug 14 02:24:08 EDT 2007
--On 13. August 2007 13:03:59 -0400 Tres Seaver <tseaver at palladion.com>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Andreas Jung wrote:
>> --On 13. August 2007 07:27:01 +0200 Andreas Jung <lists at zopyx.com> wrote:
>>> --On 12. August 2007 19:53:57 +0200 Andreas Jung <lists at zopyx.com>
>>>> to make it short: I propose to move the Zope 2 bugtracker to
>>>> Launchpad. Since the Zope 3 bugtracker works already with success on LP
>>>> we should follow with the Zope 2 bugtracker. Objections?
>>> One could also move the CMF bugtracker to LP at the same time. Then only
>>> the APE and the PAS trackers would remain. The PAS tracker is already
>>> empty and the APE tracker is also pretty much obsolete and contains only
>>> a few items.
>> And there is also the zope.org website tracker which could be migrated.
>> The guys from Canonical suggested also to migrate all these trackers
>> in one run.
> I would prefer to do this only if it is possible to have old collector
> URLs redirected automagically to the corresponding launchpad URL: there
> are too many changelog entries, etc., which refer to the current
> collector URLs.
There is already a redirection mechanism for the old Zope 3 bugtracker in
> One question came to today: we must have some redirection mechanism
> on zope.org for redirecting URls referring tickets in the old system to
> new tickets numbers within LP. We could get some mapping old-ticket-number
> -> new-ticket-number as a result from the migration?
I was planning on using the same system as we used for the Zope 3 import.
Launchpad allows a "nickname" to be assigned to each bug report. For
the Zope 3 bugs, we assigned "zope3dev-NNN" where NNN was the old bug
number. Browsing to https://bugs.launchpad.net/bugs/zope3dev-NNN
takes the user to the appropriate Zope bug. Jim then set up Apache
rewrite rules on www.zope.org to redirect the old bug URLs to
Launchpad using the nicknames.
The same will be done for your bug import, so it should be a simple
matter of copying and adjusting the existing rewrite rules on
www.zope.org to handle Zope 2 bugs too.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 186 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20070814/4aa73821/attachment.bin
More information about the Zope-Dev