On Wed, 2008-01-23 at 08:02 -0500, Ales Hvezda wrote:
> > Did anyone consider using launchpad for tracking gEDA bugs? Just
> > recently I used it to report a bug and it is definitely a lot nicer
> > to use than the bug tracker on sourceforge...

I'm agnostic to this at the moment. I'm not a fan of the SF bug tracker,
but there would of course be effort required in the change.

> I'd be willing to entertain a transition to launchpad if:
> 
> 1) Somebody (or somebodies) volunteers to migrate all the existing sf
>    bugs to launchpad.

It is something the launchpad team can do.. Out of curiosity, I asked
some of these questions, and have these answers:


>         Is it possible to import from the sourceforge trackers?
> Yes, it is possible. 

> The process to do that is to file a question in Launchpad answer tracker:
> https://answers.launchpad.net/launchpad/+addquestion
> 
> The process isn't automated. What usually happens is that we'll run the 
> importer for your project and you can review the results on a demo server. 
> When you decide to make the switch, we import them in the production 
> database.

>         If so, is it possible to keep the same bug numbers?
> No, it's not possible. 

> Once imported in Launchpad, the bugs will have new bug numbers. But a link to 
> the SF bug number will be preserved in the form of a bug watch. So it will 
> still be possible to find the relevant LP bug from the SF bug number.


>         Is it possible to differentiate bugs from feature requests and
>         patches?
> Yes, but in a different way then SF. 

(There was no further response on this.. I'm guessing it might involve
adding tags to those bug reports).

> 2) The owners of the new bug tracker on launchpad are geda-developers
>    group on launchpad.

Would be no problem as far as I can see.

> 3) Somebody provides some really compelling reasons why the launchpad
>    bug tracker is so much better than sf.

I'm agnostic.

> 4) On launchpad there has to be an easy way to dump the contents
>    (i.e. backup) of all the bugs.  Currently sourceforge does have a
>    pretty easy mechanism for this.

I'll have to ask about that. There is nothing I can immediately think of
which springs to mind.

> Item #1 is really the most important, as I have had my fun of migrating the
> bug database from jitterbug to sf.

How did the bug numbers change in that situation?


-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)



_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to