Re: [Audacity-devel] Is this really an Essential change?

[Gale A. <ga...@au...>]

| From Martyn Shaw <mar...@go...> 
| Mon, 21 Jan 2008 01:06:48 +0000
| Subject: [Audacity-devel] Is this really an Essential change?
> If Chains makes it into 1.4.0, by accident or design, they probably 
> have faults (but I don't remember what).  As Leland said, 'I also 
> don't see chains as a novice level feature'.  Maybe including them 
> into the release would drag in non-novice level comment and 
> suggestions / contributions that would improve the code?

We can't have features going into 1.4.0 "by accident". I have seen 
relatively few adverse comments about chains, mostly they are 
positive. Some of the adverse comments I have seen are about 
not all the parameters getting passed through to the chain or not
being remembered when the chain is used next time. The most 
common complaint is undoubtedly that when applying a chain to a 
string of files, we should clean up the temporary files after each 
file is processed, so as not to leave a full drive before an unattended 
batch processing is completed. Is it a major problem to change this? 

If we don't know what the problems with chains are then we should
try and find out, by specifically asking our testers to look at this 
now. If the ones discovered are fairly minor we can release note
those we can't fix easily. If there are major problems we can't fix 
easily/quickly then we have a basis on which to decide to leave 
batch out. But we do need to know one way or the other soon. 



Gale