Progress with Cart:

Aaron Bentley aaron.bentley at utoronto.ca
Fri Oct 12 00:04:26 BST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Staffan Gimåker wrote:
> On Thursday 11 October 2007 22:59:13 Aaron Bentley wrote:
>> - Doesn't allow tickets to have a priority assigned to them, in the
>>   sense of an order than the tickets should be resolved in.  What Trac
>>   calls "priority", I would call "severity".
> 
> For the sake of fairness I feel obliged to point out that this claim is simply 
> not true. Tickets in trac can have both a priority field and a severity 
> field. Furthermore, which priorities/severities to use can be configured 
> (through web- or tracadmin).

In point of fact, I'm fully aware that tickets in Trac can have both a
priority and a severity, and that the levels of these are configurable.
 None of this negates the truth of my statement.

> For example, my trac project has the following priorities: lowest, low, 
> normal, high, highest.

Right.  But the *defaults* are "trivial", "minor", "major", "critical"
and "blocker".  And these sound like descriptions of severity, not
priority.  It *may* follow that a "major" bug should be addressed before
a "trivial" bug, but it may not.

No matter how many levels of priority you have, I don't think it's
enough, because ideally, every ticket in the system has a different
priority.  So that priority can be a list of the precise order in which
tickets should be resolved.  So it can actually say: "First we do a,
then b, then c, then d...".  In Trac, there is no way to achieve that
kind of control without creating a priority level for every ticket in
the system.  So in Cart, priority is an integer.  I also considered
using linked lists.

> I'm very interested in considering and trying out your alternative once it 
> matures a bit. I'd probably be reluctant to ditch our pretty and "branded" 
> trac before you can show prettier screenshots :)

That's sensible.  There is still plenty of work to be done.

> Do you have any plans on supporting plugins in the future?

Hadn't really thought about it, but I can't see why not.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHDqv60F+nu1YWqI0RAjFXAJ0ZZKiS3jX45ORz+IjxkXhkL+DsZQCeN3ve
3KbPTRpqiyEF0FQ6QYGhRfc=
=KkWt
-----END PGP SIGNATURE-----



More information about the bazaar mailing list