Logging into Roundup

If you have ever used your SourceForge account on the old Python bug tracker, you also have a Roundup account. To get your password, you need to go through the "forgotten password" procedure (even though you really did not forget it on SF we do not have access to it for the Roundup tracker). On the tracker, go to "Lost your login" (XXX hyperlink), and enter your SF username into the Username field.

This will send you an email (Confirm reset of password for Tracker), where you need to follow the link. You will get another email (Password reset for tracker) which contains the new password. The two-email procedure prevents somebody else malicously resetting your password.

You then might want to change your password. You can also change the email address, so that emails won't get sent through sourceforge.net anymore.

Getting a Developer account under Roundup

XXX

About Differences between SF and Roundup

[http://roundup.sourceforge.net/ Roundup] is not hugely different from SourceForge in terms of usage. Because the initial transition is mostly for resource reasons (i.e., to control our own tracker), the information presented for issues is almost identical to what the SF tracker had.

The largest change people will notice, though, are the additions of some Roundup-specific fields. Those are denoted with NEW in their descriptions. All of them help with the management of bugs and thus should be used when possible and even filled in on existing issues brought over from SF.

Another change is that of monitoring. SF had a monitor button that subscribed you to an issue so that you always received an email on all updates. That is now replaced by the nosy list. By entering your username on the nosy list you will receive an email every time the issue is changed. More details can be found in the explanation of the field.

Lastly, Roundup provides an email interface to issues. This means that you can actually post to issues by simply replying to an email that you receive. This makes posting replies very easy as one does not need to go through the web interface if the reply does not involve changing fields or uploading files (which can be done through email as well).

If there is a problem

If you encounter a problem with the tracker (both in terms of it running and the transition), please create an issue at the [http://psf.upfronthosting.co.za/roundup/meta/ meta tracker]. Tracker-discuss (which is discussed below) will be notified and it will be dealt with as best as possible.

Improving the tracker in the future

Please remember that the initial transition is not meant to drastically change how issues are handled or reported. It is simply to get Python's issue tracker under the control of the PSF. With that in place, discussions can begin about improving the handling of issues.

After the transition is complete and stability has been proven then discussions can begin in earnest to improve the handling of issues. To participate in such discussions, please subscribe to the [http://mail.python.org/mailman/listinfo/tracker-discuss tracker-discuss] mailing list. This list is meant to discuss the improvement and maintenance of the various trackers hosted by python.org.

Fields

Classification

Title

Exactly what it sounds like.

Type

Specify what kind of issue it is (crasher, compile error, etc.).

Severity

DIFFERENT: How severe is the problem; nuisance or critical? There are fewer options compared to SF (five down from 10).

Components

DIFFERENT: What area of Python is the issue dealing with? This section allows for multiple selection.

Versions

DIFFERENT: The specific versions that are affected. This is a multiple selection box so all known versions that are affected can be set.

Process

Status

DIFFERENT: Specify whether the issue is open, pending (being actively worked on), or closed.

Resolution

Resolution once the issue is closed.

Dependencies

NEW: If the issue depends on another issue(s), list them here. A complete list of issues can be found by clicking on the list link.

Superceder

NEW: If the issue is superceded by another issue, list it here. The list link pops up a window to help find the superceding issue.

Assigned To

Who is in charge of the issue.

Nosy List

NEW: List of usernames of whom will be notified when anything changes on the issue. The original poster (OP) is automatically added. (XXX make commenters automatically added to list).

Priority

How quickly must this bug be fixed? Different from Severity by specifying how quickly it must be dealt with, not how severe the issue is.

Keywords

NEW: Multiple selection list of keywords to set to help classify the issue.

• py3k: Issue is only relevant for Python 3

  patch: Issue has a patch attached (or was imported from the SF patches tracker)

  needs doc: Patch is missing documentation changes

  needs test: Patch is missing test suite changes

CategoryTracker