Opened 11 years ago

Closed 11 years ago

#25 closed task (worksforme)

Migrate Bugs from SourceForge

Reported by: rlaager Owned by: lschiere
Milestone: 2.0.0 Component: pidgin (gtk)
Version: 2.0 Keywords:


What's the plan for migrating bugs from SourceForge?? Do we need to write something to do an import from a database dump?

Alternatively, should we just mass update bugs notifying people to post a new bug to Pidgin's Trac? This has the advantage of ensuring we can still contact the submitters (though we could import "their username @" as their e-mail address).

I've long been suggesting that we use this transition as an opportunity to flush our trackers and start anew. Maybe that's not a good idea.

Change History (1)

comment:1 Changed 11 years ago by lschiere

  • Resolution set to worksforme
  • Status changed from new to closed

I have been planning on simply mass updating the bugs. I want to do this for several reasons

1)I suspect many of them will not be reopened. They are currently assigned, but have in fact been fixed, and were never closed

2)I know many of them are duplicate. If we migrate them via script, we have a tracker of the same size as the SF one to find those duplicates. If we require resubmission, the resubmissions will be spread across time, making it easier to find the duplicates as they come in.

3)The categories in trac do not exactly match those in sf, nor do I want them to. The categories and groups in sf are a kuldge to try to make up for its flaws. As the resubmits come in, I want to try to get them categorized appropriately. Again, this would be harder to do if it happens all at once.

4)some trackers, like the rfe tracker, badly need a purge regardless.

5)some trackers, like the plugins tracker, will have no replacement. They will get a different canned message with their mass update.

On the downside, this will upset a number of users. But I have been closing out bug reports related to old versions systematically anyway, so it is not *too* different from that policy. I think on the whole the benefits outweigh the costs.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!