|
Size: 2013
Comment:
|
← Revision 43 as of 2009-09-17 11:55:58 ⇥
Size: 1026
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| 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. | 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. |
| Line 5: | Line 5: |
| /!\ No new trackers are being accepted for consideration. /!\ | Jira was the first choice of the committee. A lot of people complained about using a closed-source and hosted bug tracker, so a call was posted for volunteers to help administer a Roundup installation. Enough volunteers came forward, so work is now proceeding on improving the conversion to Roundup. |
| Line 7: | Line 8: |
| 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. | The Roundup bug tracker that serves http://bugs.python.org/ is actually hosted at http://psf.upfronthosting.co.za/roundup/tracker/ |
| Line 9: | Line 10: |
| 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) || ||TracTracker||http://python-trac.swapoff.org||Alec Thomas||alec@swapoff.org|| ||[http://www.mechanicalcat.net/tech/roundup/wiki/PythonTracker Roundup]||http://efod.se/python-tracker/||Stefan Seefeld||seefeld@sympatico.ca|| || JiraTracker || http://jira.python.atlassian.com || Jonathan Nolen || jonathan@atlassian.com || || LaunchpadTracker || https://demo.launchpad.net/products/python/+bugs || James Henstridge || james.henstridge@canonical.com || 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. = Key Wiki Pages = * GoodTrackerFeatures * WorkingWithSourceForgeData * AndrewKuchling/TrackerNotes |
Bugs found in the living installation of Roundup for Python bugs are reported to '''meta-tracker''' -- is at http://psf.upfronthosting.co.za/roundup/meta/ Please report problems with the bug tracker there. |
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 SourceForge for use by the Python development team. A copy of that request can be found at OriginalCallForTrackers.
Jira was the first choice of the committee. A lot of people complained about using a closed-source and hosted bug tracker, so a call was posted for volunteers to help administer a Roundup installation. Enough volunteers came forward, so work is now proceeding on improving the conversion to Roundup.
The Roundup bug tracker that serves http://bugs.python.org/ is actually hosted at http://psf.upfronthosting.co.za/roundup/tracker/
Bugs found in the living installation of Roundup for Python bugs are reported to meta-tracker -- is at http://psf.upfronthosting.co.za/roundup/meta/ Please report problems with the bug tracker there.