Brett Cannon writes:
> In my dream schema, severity becomes
Then how does the user indicate how important it is to him? My
severities (in an experimental roundup tracker I'm implementing) are
'inelegant', 'inconvenient', 'some work obstructed', 'much work
obstructed', 'security', 'data loss',
Georg Brandl wrote:
> Christian currently does a good job of assigning the correct properties
> to new bugs. In any case, I'd prefer to keep a way to mark a bug as
> "high-priority" (meaning that it should be fixed before the next release)
> even if most of the bugs don't have an assigned priority.
Martin v. Löwis schrieb:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and indicates how serious the issue
> impacts him an
On Jan 20, 2008 10:42 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and ind
Martin v. Löwis wrote:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and indicates how serious the issue
> impacts him and
After some months of tracker operation, I'd like to discuss one aspect
of the tracker schema: priorities.
Each issue has a severity and a priority. The severity is assigned by
the submitter, defaults to normal, and indicates how serious the issue
impacts him and the community.
The priority is ass
