Re: [Fresco-devel] issue tracking: Request For Comments

> I'm in the process of setting up an issue tracker for fresco,
> and I'm designing the entities and their relationships we should
> use. Therefor I'd like to get your feedback. Here are the types
> I'd like to use:
Does this mean you're just in the process of customizing roundup for
Fresco's use or are you embarking on a new solution?

I have a few questions that might or might not be relevant (and many
apologies if they're not at all relevant):

- Roundup doesn't seem to mesh with CVS (only one mention of it that I can
find in the documentation); is there a way to have it keep track of exact
CVS commits that correlate with issues in this system?  This would be nice
to find exactly when/where/by whom the bug was handled through the CVS
tree.

- As an aside, wouldn't it be nice to have sample systems doing full
compiles nightly the way that mozilla does?  Or am I just ignorant of this
already happening?  It looks as if it would be trivial to write a python
script to label each with a green/yellow/red light to tell whether a
certain patch broke the tree or not (or was still compiling, with a
yellow).

- Would it be possible to attach my 'interest' to an issue in the system
so that whenever anyone does anything to the issue, that I get emailed?
There might be a way to do this if I listed myself as the developer who
was working on an issue...?

- Would this be a good time to institute a way of keeping track of who
touched what?  This would be helpful in the future if anyone wanted to
change the license of the code and wanted approval of everyone who
actually changed it.  This doesn't seem likely to happen, but is a
definite what-if scenario.

Other than my reveries above, your list seems very complete and I can't
think of anything to add to it, except that I can imagine that bug's
'type' attribute will probably need to be expanded from time to time.


 - - - - - - - - - - - - - - - - - -
           Sean Rae / es9
        cool and calculating
       www.birdnest.org/raes1
 - - - - - - - - - - - - - - - - - -