----- Original Message ----- From: "Steve Loughran" <[EMAIL PROTECTED]>
[...] > maybe so, but we also field many user bug requests with 'update to nightly > build' messages, and then because of deprecation messages encourage the > users to upgrade to attributes which we then take away. Is that a fair thing > to do? > The problem is that if we take it away, projects built with a version of > 1.5alpha will break. it may be tomorrow, it may be in six months when the > user pulls out a copy from CVS. The latter is worse as they may not know > what on earth happened, especially if they were not the original build file > author. It'll be support calls one way or the other. Come on, Steve, there is something fundamentally wrong here. Alpha has never been intended for production use. If user use it they must know exactly what they are doing, you cannot get experimental software and ask for stability at the same time... What should we do otherwise ? stop developpement ? create a branch for maintenance and another one for experiments and refactoring ? keep all the thing that we commited once in CVS, this is hard. > I prefer leaving them in with a deprecation message, though removing all > documentation of their very existence from the manual pages. > Likewise, I would like to clean up the manual to strip out <execon> > <rename>,<deletefiles> , maybe even the whole global filter thing. obsolete > task names and dangerous ideas do need to be kept out of site. The source is > still there for people to look at. +1 Stephane -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
