[Tracker-discuss] schema ideas

Paul Dubois pfdubois at gmail.com
Wed Nov 15 19:19:12 CET 2006

FWIW I added a 'Due Date' to our tracker by following the example in the
Roundup guide. However, I decided not to use an actual date field but rather
strings, so that you can have due dates like "v2.6", "ASAP", and "2Q 2007";
the problem with real dates was that releases do not tend to have stable
dates. Using the ordering attribute you can control the order of the groups
in a custom search by due date. I added a permission class to give to those
special managers allowed to create new 'due dates'.

As I mentioned before we use a special priority to indicate things that have
been fixed but are not yet in the main line; but perhaps in the Python
context that would be irrelevant. A due date can indicate when the fix or
enhancement will appear.

On 11/15/06, Georg Brandl <g.brandl at gmx.net> wrote:
> Stefan Seefeld schrieb:
> > Anthony Baxter wrote:
> >> Speaking for myself - we use priorities to mark "stuff which needs
> >> to be looked at before release X.Y" and the like. This could, and
> >> should, be better implemented using keywords.
> >
> > What's the advantage of using keywords for this instead of a more
> > structured approach where the bug either has a property of type
> > 'target version', or where there is another entity 'release' or
> 'milestone'
> > that refers to all bugs to be closed ?
> > The latter has the advantage of being more expressive, so you could
> > form more complex queries more easily (either online, or when
> > generating reports, etc.).
> The milestone concept is already weakly used with the SourceForge groups.
> IMO it's a good concept, helps you keep track of which bugs should be
> closed
> before which release. Together with a priority/type classification
> (showstopper,
> major bug, minor bug, nuisance, enhancement request), there might be a
> better
> possibility to establish guidelines on which bugs must be looked at before
> release.
> regards,
> Georg
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061115/ea025982/attachment.htm 

More information about the Tracker-discuss mailing list