more work to be done....

Christopher R. Hertel crh at
Thu May 17 19:11:51 GMT 2001

> On Thu, 17 May 2001, Christopher R. Hertel wrote:
> > > But... why not use an actual bug tracking system?  It may be more effort to
> > > set up, but in the long run it may be a better solution.
> >
> > Tridge even wrote a bug tracking systems once.  The problem is, our
> > development model doesn't match the bug-tracking model.  We don't assign
> > priorities to bugs or bugs to coders.  We each tackle the problems which
> > growl at us loudest and which we are most capable of taming.
> Ah...this is an excellent point.  I'm not really worried about assigning
> priorities to bugs.  I'm just tired of having to write.  "Known
> bug in 2.X.X ...fixed in CVS"  Users would appreciate this as well
> so they don;t spend time tracking down known issues.

The only difference between this and a BBS type-o-thang is that folks 
would have a place to enter comments, a la slashdot.  Perhaps, instead of 
a slashdot sort of thing, people could mail comments to an address like 
samba-buglist at  The subject would contain the bug number and 
the message would be attached to the bug for *optional* reading.  This 
might cut down on "anonymous coward" messages.

Point is, when we come across a bug we often need lots of input from the 
field to nail it.  This would provide a mechanism for gathering such 
information without clogging the samba-tech list.

Having said that, there are also advantages to discussing bugs on the tech
list, and there are also issues with managing something like a BBS. 

I guess I'm tossing ideas to see if they land face up.

Chris -)-----

Christopher R. Hertel -)-----                   University of Minnesota
crh at              Networking and Telecommunications Services

    Ideals are like stars; you will not succeed in touching them
    with your choose them as your guides, and following
    them you will reach your destiny.  --Carl Schultz

More information about the samba-technical mailing list