Re: [IAEP] [Sugar-devel] (Please read) Re: Proposed Trac - > Launchpad migration
On Mon, Nov 2, 2009 at 10:11 AM, Paul Fox wrote: > luke wrote: > > On Sun, Nov 1, 2009 at 19:06, Paul Fox wrote: > > > > > so, if i understand this, the text of the bugs will still contain lots > of > > > bug numbers that link correctly, but read incorrectly. > > > > > > Well, Launchpad will redirect to the proper number. > > > > > > > I guess there's no way to simply edit the bug text during the import, so > as > > > to make the > > > references correct w/o redirection tricks? > > > > > > I'm not really sure what you mean. Are you referring to the references to > > other bugs inside the bugs themselves? > > yes. > > > Possibly, although it would be easy > > to mess up. > > i've recently found myself (on dev.laptop.org) referencing other > bug numbers from within the comment text: e.g., "I wonder if > this bug is related to bug #1234?". if the old bug #1234 is the > new bug #4321, then presumably your fixes would cause the "#1234" > to link to the new bug system's "#4321" bug, if i click on it, > but it will continue to _say_ "1234. this is what i think might > be very confusing. Also please think about bunch of links in Wiki pages (http://wiki.sugarlabs.org/go/0.86/0.86.1_Notes for an instance). We need to retain all of the links to historical ticket to support existing users. I think just correct redirection is insufficient, reading bug number correctly is important as documentation purpose. How would you identify some ticket in IRC session, etc... /Korakurider > > paul > =- > paul fox, p...@laptop.org > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] (Please read) Re: Proposed Trac - > Launchpad migration
On Sun, Nov 1, 2009 at 2:06 PM, Chris Ball wrote: > Dear Sugar folks, > > This mail didn't get any replies, but it's important to know whether > people agree with it before going ahead. So, please understand that: > > * bugs.sugarlabs.org is moving from Trac to Launchpad. > * Existing bug data will be imported, but the bug numbers won't be the > same. > * It will be hosted by Canonical externally, rather than by SL as Trac > currently is. > > If any of these are not to your liking, the time to speak up is now, > before it all happens. :) > > Thanks for reading, > > - Chris. > -- > Chris Ball > One Laptop Per Child > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > What's the reason for this migration? -- Sameer ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] (Please read) Re: Proposed Trac - > Launchpad migration
On Sun, Nov 1, 2009 at 19:06, Paul Fox wrote: > so, if i understand this, the text of the bugs will still contain lots of > bug numbers that link correctly, but read incorrectly. Well, Launchpad will redirect to the proper number. > I guess there's no way to simply edit the bug text during the import, so as > to make the > references correct w/o redirection tricks? I'm not really sure what you mean. Are you referring to the references to other bugs inside the bugs themselves? Possibly, although it would be easy to mess up. -- Luke Faraone http://luke.faraone.cc ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] (Please read) Re: Proposed Trac - > Launchpad migration
On Sun, Nov 1, 2009 at 18:19, Paul Fox wrote:
> > * bugs.sugarlabs.org is moving from Trac to Launchpad.
> > * Existing bug data will be imported, but the bug numbers won't be the
> > same.
>
> what happens to bug numbers (i.e., referring to other bugs in the
> current database) that are embedded in the text commentary? i
> assume they get converted, but it's worth asking.
Good question.
There are two ways we can do this:
1. Ask for a list of the new bug numbers, and do some apache mod_redirect
magic to convert them to the new method.
2. During the import, give each imported bug an alias, like 'sl1234'
which identify their numbers on the old bug tracker. Then we just have to
redirect from http://dev.sugarlabs.org/bugs/1234 to
https://launchpad.net/bugs/sl1234, and LP will handle the rest.
I'll have to ask for confirmation on whether option 2 can be automagically
done during the import We'd have to implement the redirect to ("
launchpad.net/bugs/sl" + BUG_NUMBER) ourselves, but that's trivial.
Worst case, we can do 1. I'll follow up and see what's doable and report
back to the list.
--
Luke Faraone
http://luke.faraone.cc
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep
