Please convert bug database from sorurceforge.net

Asked by Dick Hollenbeck

Can you please import the sourceforge bug tracker information into project "Kicad" Bugs?

Input file has been run through the conversion script and is here:

http://softplc.com/dick/output.xml

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Graham Binns
Solved:
Last query:
Last reply:
Revision history for this message
Deryck Hodge (deryck) said :
#1

I did a local import which worked fine, so the output file looks good. As soon as we have sys admin availability, I'll run the import against our staging server, and ping back here for you to take a look. If the bugs look okay, we can then proceed ahead with the real import.

Cheers,
deryck

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#2

deryck,

We had a question about whether the conversion program bundles in the sourceforge tracker's "Feature Requests" or just the "Bugs". (And if we wanted it to or not.) The best solution depends on what launchpad offers in terms of a place for "Feature Requests". What do you suggest?

Revision history for this message
Deryck Hodge (deryck) said :
#3

I'm not sure how the sf conversion script handles SF's feature requests, if at all. Maybe Graham could comment on this?

As for how we do feature requests on Launchpad, each project does it differently. Some use the WISHLIST status; some use a "feature" tag; some use a combination of both these approaches; and then some use blueprints to track feature work beyond just the request.

Hope that helps.

Cheers,
deryck

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#4

It would be nice if the conversion program could fill the "importance" field for tracker_items coming from "Feature Requests" instance of the tracker with "WISHLIST".

I have confirmed that the "Feature Requests" are coming through the conversion program into the "output.xml" bugs, but they are not clearly marked as feature requests in the way you suggest. Is there anybody who is able to enhance the conversion program in this way easily? My python is too rusty.

Here is the input file:

http://softplc.com/dick/kicad_export.xml.bz2

Revision history for this message
Graham Binns (gmb) said :
#5

On 9 April 2010 18:04, Dick Hollenbeck
<email address hidden> wrote:
> Question #106874 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/106874
>
> Dick Hollenbeck gave more information on the question:
> It would be nice if the conversion program could fill the "importance"
> field for tracker_items coming from "Feature Requests" instance of the
> tracker with "WISHLIST".
>
> I have confirmed that the "Feature Requests" are coming through the
> conversion program into the "output.xml" bugs, but they are not clearly
> marked as feature requests in the way you suggest.  Is there anybody who
> is able to enhance the conversion program in this way easily?  My python
> is too rusty.

I can take care of this on Monday, no problem. I've filed bug 559439
about this to keep track of it.

Revision history for this message
Deryck Hodge (deryck) said :
#6

There is a test import up for review at: https://bugs.staging.launchpad.net/kicad

I made a mistake and imported the original file, not the updated file after the feature request discussion. However, I think it's worth reviewing for spotting other errors, if you don't mind.

If it looks good, we can do the feature request one after staging updates again. Or we can do a new file if you spot other errors.

Cheers,
deryck

Revision history for this message
Graham Binns (gmb) said :
#7

I've now update the script. If you run it with the
--wishlist-feature-requests option it will give all Feature Requests
an importance of Wishlist.

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#8

deryck,

I have updated the file "output.xml" using the modified script with the
special command line option.

I am unable to get to the server that you mention currently. Can you re
do the import using the updated file, and I will check it when I can,
and when your staging server is back up. I have no reason to make the
import perfect, but I appreciate the ability to review the import before
we go live with it.

Thanks,

Dick

Revision history for this message
Deryck Hodge (deryck) said :
#9

Hi, Dick.

Yeah the staging server is updating currently. It can happen frequently, since it's for staging new code. I'll get the bugs imported sometime tomorrow and ping you again here.

Sorry we missed your question on IRC. I just now saw your question there.

Cheers,
deryck

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#10

deryck,

I noticed that all the bugs are imported as status:New.

Can we do a search and replace using a text editor on output.xml and get
everything to import as status:Triaged.

This way we can tell the difference between the old and new bugs.

<status>NEW</status> becomes <status>TRIAGED</status>

This, plus the WISHLIST change, should be good enough.

DIck

Revision history for this message
Deryck Hodge (deryck) said :
#11

Hi, Dick.

Yes, I can make this status change on your most recent output.xml file. I can't do a new import on staging until the DB resets. We're still waiting on that. When that happens, I'll do a fresh test import run and ping back here.

Cheers,
deryck

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#12

Thank you Deryk for the commitment to handle this.

We are getting folks who want to post new bugs, I've held them back
because the database is not ready. The sooner the better on this now.

Dick

Revision history for this message
Deryck Hodge (deryck) said :
#13

Hi, Dick/

I did a staging import Thursday and everything went fine with it. Unfortunately, the staging DB reset before I could ping back here. This happened late in the day Thursday for me, and I was off Friday with family vacation, which is why it slipped until the DB restore. Also, we cannot work on bug imports this week due to the coming Ubuntu release and limited sys admin availability. We will take up bug imports again next week.

Sorry this is taking so long. As noted on IRC previously, you can add new bugs to Launchpad with no effect on the bug import.

Cheers,
deryck

Revision history for this message
Launchpad Janitor (janitor) said :
#14

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Binns (gmb) said :
#15

Unexpiring; we've not been able to get to this due to a lack of sysadmin availability because of the Ubuntu release.

Revision history for this message
Graham Binns (gmb) said :
#16

Reopened

Revision history for this message
Graham Binns (gmb) said :
#17

Hi Dick,

I'm going to try to get this imported onto staging for you today. Is the file above the latest version of your bug export?

Cheers,

Graham

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#18

Graham Binns wrote:
> Your question #106874 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/106874
>
> Status: Open => Needs information
>
> Graham Binns requested for more information:
> Hi Dick,
>
> I'm going to try to get this imported onto staging for you today. Is the
> file above the latest version of your bug export?
>
> Cheers,
>
> Graham
>
>
Yes, at the softplc.com URL.

Dick

Revision history for this message
Graham Binns (gmb) said :
#19

These bugs have now been imported into staging. Please check them over and let me know if there are any problems. If not, we'll proceed with the import to production.

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#20

Graham Binns wrote:
> Your question #106874 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/106874
>
> Status: Open => Needs information
>
> Graham Binns requested for more information:
> These bugs have now been imported into staging. Please check them over
> and let me know if there are any problems. If not, we'll proceed with
> the import to production.
>
>
Graham,

Let's do the production import now.

Marginally related question: how do I expand the list of "Products"
under the UI's "Affects" choice? There are a number of programs within
this project, and the old sourceforge bug database let us pick a
specific program that the bug applied to.

Thanks, this is going to be nice to have when its done.

Dick

Revision history for this message
Launchpad Janitor (janitor) said :
#21

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Graham Binns (gmb) said :
#22

Unexpired. We'll hopefully have time to deal with this after next week's Launchpad rollout.

Revision history for this message
Launchpad Janitor (janitor) said :
#23

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#24

         "We'll hopefully have time to deal with this after next week's Launchpad rollout."

Actions speak louder than words. Pretty impressive, going on sixty days now without any action.

Revision history for this message
Graham Binns (gmb) said :
#25

You're quite right; I dropped the ball on this. My apologies.

I'll deal with this first thing Monday morning UK time.

Revision history for this message
Deryck Hodge (deryck) said :
#26

Dick,

This request has not been 60 days without any action. It has been one week since the rollout Graham mentioned. Yes, we did drop the ball after rollout. Yes, it is taking a long time to get this done. I am very sorry about this, and I am as anxious as you that our team close this request. Graham, please make this a priority until it is finished.

While I understand your frustration, to accuse us of no action for 60 days is untruthful and unhelpful. We have done 3 test imports into staging and also updated the converter script to handle SF's feature requests as wishlist, per your request/suggestion. The last time I chatted with your on IRC, you acted as if doing the import was less of an issue as long as being able to enter new bugs was possible. I know that you and I have discussed this import a couple times or more on IRC. I do feel we have been attentive to your requests and comments and tried to be as responsive as we could alongside all our regular development work and bug import requests by other users. Bug imports naturally have a lot of back-and-forth between the requesting user and our team, so this always takes longer than everyone likes. It's not an ideal system for us and we hope to change it one day, but for now, it's what we have.

Again, I'm sorry you have had a bad experience. I hope we will be done today. I hope, too, that you can see that we have been trying to work with you over the last two months throughout the life of this request.

Cheers,
deryck

Revision history for this message
Best Graham Binns (gmb) said :
#27

The bugs have now been imported into production. Please let us know if there are any issues with the production data.

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#28

Thank you.

Revision history for this message
Dick Hollenbeck (dickelbeck) said :
#29

Thanks Graham Binns, that solved my question.