[Tracker] [Pidgin] #25: Migrate Bugs from SourceForge
Pidgin
trac at pidgin.im
Mon Nov 6 23:16:33 EST 2006
#25: Migrate Bugs from SourceForge
---------------------------+------------------------------------------------
Reporter: rlaager | Owner: lschiere
Type: task | Status: closed
Priority: major | Milestone: Go public with Pidgin 2.0.0
Component: pidgin (gtk) | Version: 2.0
Resolution: worksforme | Keywords:
---------------------------+------------------------------------------------
Changes (by lschiere):
* status: new => closed
* resolution: => worksforme
Comment:
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.
--
Ticket URL: <http://developer.pidgin.im/ticket/25#comment:1>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list