tcllib-devel

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

[Larry W. V. <lv...@ca...>]

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.
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

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: Tuesday, November 27, 2001 4:09 AM
> To: tcl...@li...
> Subject: [Tcllib-devel] How would tcllib developers prefer to hear about
> problems in the development branches of the code?
>
>
>
> 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 ?

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

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

[Jeff H. <Je...@Ac...>]

> 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 ?

It depends on the problems.  Minor problems with commited changes
should likely be just addressed to the commiter.  Problems that
expose design weaknesses should be sent to the list as a whole.

Don't ignore problems.  Don't assume the commiter will be aware
of them.

Jeff