RE: [Tcllib-devel] How would tcllib developers prefer to hear about problems in the development branches of the code?

[Andreas K. <and...@Ac...>]

> -----Original Message-----
> From: tcl...@li...
> [mailto:tcl...@li...]On Behalf Of Larry W.
> Virden
> Sent: Wednesday, November 28, 2001 1:27 AM
> To: tcl...@li...
> Subject: Re: [Tcllib-devel] How would tcllib developers prefer to hear
> about problems in the development branches of the code?
>
>
> From: "Andreas Kupries" <and...@ac...>
>
> > > [mailto:tcl...@li...]On Behalf Of Larry W.
> > > Virden
> > >
> > > During development, one commits code changes to the CVS as work
> > progresses.
> > > How would you developers like to learn about problems with this code?
> > > Not at all?
> > > Private email messages?
> > > Formally submitted bug reports ?
> >
> > > Just curious as to what the preferred mode of operation should be.
> >
> > Can you give us a bit more context to this general question ?
>
> I am uncertain exactly how much more context I can give.  Let's see.
> Often I see people on comp.lang.tcl and elsewhere recommended to get the
> latest version of tcl/tk/tcllib/etc. from the CVS when they are
> seeing problems.
> In this way, they can see if their problems are fixed in the
> latest version.
>
> However, I have also seen times in the past when someone says "Oh, such
and
> such a doc/example/demo/test case/aspect of the extension or  language
doesn't
> work" and when they indicate they are using the latest code from CVS there
> is almost a shrug and "oh well, that code isn't released you know  -
perhaps
> all the changes haven't been checked back in, the code checked into the
> CVS isn't intended to be a real distribution - there are files  that need
to
> be generated, etc." .
>
> These latter are all fair and true statements.  However, I know that I,
> as a part time developer, am left wondering exactly what procedure I
should
> follow with regards to reporting the large number of problems in tcllib's
> test suite for instance.

Ok. For me I would dismiss the "Not at all" option. Problems are problems,
even if they are in code under ongoing development. There is no way to
predict
if the author will see the same problem.

So at least a private email should be send IMHO. If there is a place for
formal
bug reports I would log one at that too ...

Regarding the tcllib testsuite ... Format bug reports are in order.


--
	Andreas Kupries <and...@Ac...>
	Developer @ http://www.ActiveState.com