[Sugar-devel] (Please read) Re: Proposed Trac - > Launchpad migration
Korakurider
korakurider at gmail.com
Sun Nov 1 22:54:21 EST 2009
On Mon, Nov 2, 2009 at 10:11 AM, Paul Fox <pgf at laptop.org> wrote:
> luke wrote:
> > On Sun, Nov 1, 2009 at 19:06, Paul Fox <pgf at laptop.org> 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, pgf at laptop.org
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
More information about the Sugar-devel
mailing list