[Python-Dev] SF tracker groups ongoing... (original) (raw)
Fred L. Drake, Jr. fdrake@acm.org
Tue, 23 Apr 2002 00:39:16 -0400
- Previous message: [Python-Dev] SF tracker groups ongoing...
- Next message: [Python-Dev] SF tracker groups ongoing...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anthony Baxter writes:
At the moment we have the following tracker groups: ... Can these be cleaned up a lot? merge Python 2.1.1 and 2.1.2 into Python 2.1.x, merge Python 2.2 and Python 2.2.1 candidate into Python 2.2.x. We'd need to mass-move the existing entries to them first, tho. I believe this needs one of the SF admin users to do this...
The version-specific groups are all relatively new. I'm not aware of anyone really discussing this or thinking through a policy about these. I don't think we can remove any of these, but we should definately consider using "2.x.y" instead of "2.x.1", "2.x.2", etc.
Also, why do we have Groups like '3rd Party', 'Feature Request', 'Irreproducible', 'Not a Bug', 'Platform-specific', and 'Trash'? Some of these seem like resolutions, Feature Requests have their own tracker.
The migration from the "old" SF bug & patch trackers was done poorly (when measured against any particular project); they managed to "merge" different fields from the two old trackers in what they thought was the right way (or maybe it happened by accident), and it didn't seem to turn out very well. The fact that the "Group" and "Resolution" kind of overlap is a result of this.
On the subject of trackers, if FRs are merged into the main tracker then 'group: feature request' makes sense. I'd hope that merging them should be a matter of a database update at SF, to change the 'atid' of the existing items... has anyone asked SF if it's possible?
No idea. Is anyone planning to do such a merge? I think I'm the only one who's commented that the FR tracker is a bad idea. (The default setup for a project on SF is definately too "heavy" for my taste, but they are probably thinking of what makes sense for the "SF On-Site" customers. I'd hope the default setup is configurable, though!)
also, why is there an empty 'support requests' tracker? shouldn't it be deleted?
This was "provided" by SF when they released the current trackers. It's a nuisance, but I don't think they can be deleted, only made "non-public".
-Fred
-- Fred L. Drake, Jr. PythonLabs at Zope Corporation
- Previous message: [Python-Dev] SF tracker groups ongoing...
- Next message: [Python-Dev] SF tracker groups ongoing...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]