bug tracking: areas (was: [GRASS5] bugs)

[Bernhard Reiter]

--pZs/OQEoSSbxGlYw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 28, 2005 at 10:43:54PM +0100, Paolo Cavallini wrote:
> I am checking single bugs before updating from 5.7 to 6.
> I have a few requests/suggestions for the bug tracker:

Note as I have written before I hope to be able to offer a better system.
The current RT is quite hard to adapt, thus I'd rather focus to work
on the future system.

> - force area definition (users should not be able to file a bug without=
=20
> associate category)

IMO not done easily.

> - split it into two queues: grass5x and grass6x (with different links fro=
m=20
> grass web site); this would make it far easier to keep everything tidy, e=
ven=20
> if at the expenses of some replication

Two queues can be done by the tracker, but I would suggest
to use two links from the butracking page to archive the same.

> - a flag "reported/confirmed" (as suggested) would be useful

Not easily done, though I would suggest that a developer can just
add this as reply or comment to the tracker.

> - bugs might better be sorted by area+priority (from grass6 - priority 10=
0 to=20
> wish6 - priority 0) than by date

Not easily done, but you can sort by priority or filter by category.
Can you come up with the best links for the grass bugs page?

--pZs/OQEoSSbxGlYw
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCJEpMh9ag3dpKERYRAs8uAJwPBvFI6YCBF3HjtEOCl05Qk8WPmACdEQOK
+IZx3haAcOkG72FooybTEUQ=
=EC/U
-----END PGP SIGNATURE-----

--pZs/OQEoSSbxGlYw--