Hi,
Leif Mortenson wrote:
Other than the failing tests that you are citing, what is the maintenance that is needed?
My opinion is that we should not be releasing software that is not well documented, well tested and "clean"[1]. With this perspective maintainence of thread would involve;
* get decent documentation
* get near 100% unit test coverage with "deep" tests (ie about 15% jester rating).
* merge all the artifacts back into a single artifact
* if pool gets deprecated provide migration to commons-pool or whatever
* provide migration path to jdk1.5 Executors (or whatever they are called) when appropriate
* all the regular stuff. ie maintain builds as underlying tools evolve (ie gump, maven), support on mailing list, keep website uptodate
etc.
[1] excalibur-thread is not "clean" at the moment as it psuedo-maintains backwards compatibility for things dead about 2.5 years ago. We should release and then do a V2 that is a clean design.
-- Cheers,
Peter Donald
"I am not young enough to know everything."
- Oscar Wilde (1854-1900)--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
