2013
Comment:
|
2229
added link to recommendation
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
/!\ '''The infrastructure commitee has made a recommendation on Oct 3rd, 2006. See [http://mail.python.org/pipermail/python-dev/2006-October/069139.html python-dev posting] for more (selected: Jira & Roundup).''' |
About
Python Software Foundation's Infrastructure commitee put out a call for trackers (bug/request/issue/ticket trackers) in June 2006 in order to evaluate alternatives to [http://sourceforge.net/tracker/?group_id=5470 SourceForge] for use by the Python development team. A copy of that request can be found at OriginalCallForTrackers.
The infrastructure commitee has made a recommendation on Oct 3rd, 2006. See [http://mail.python.org/pipermail/python-dev/2006-October/069139.html python-dev posting] for more (selected: Jira & Roundup).
No new trackers are being accepted for consideration.
Four trackers were set up by the deadline of August 7 2006; see below for the list. A committee of four people is now looking at the submitted trackers, and will recommend one for use as the new Python bug tracker. The committee will make its recommendation in the fall, perhaps in October.
Once a tracker has been selected, a new installation will be set up and the SourceForge bug data will be converted once more. That conversion may be more carefully done than the conversion for the demo trackers.
Participating Trackers
Tracker wiki page |
Test Tracker URL |
Contact Person (name & email) |
|
[http://www.mechanicalcat.net/tech/roundup/wiki/PythonTracker Roundup] |
|||
Jonathan Nolen |
|||
James Henstridge |
To find out what the committee is finding they like about various trackers participating, please monitor GoodTrackerFeatures (to be edited by committee members only!). For those providing a test tracker, please subscribe to that wiki page so that you can see what the committee discovers they like about trackers, allowing you to change your tracker accordingly.