> * website is screwed
Have you posted a checklist of issues?
> * released components have backwards compat broken haphazardly
True. But that is being corrected. And the whole issue of compatibility
has been brought to the forefront, with a much higher profile than
previously.
> * indepent release of components is non existent
How so? I see that Avalon is pushing to go through ALL packages and release
them in dependency order as we speak.
> * docs are non existent for many components
Perpetual problem for most open source projects. I'm going to write some
config docs for tomcat/jk2 because I need to figure out answers to configure
my own system, and I might as well share them.
> * unit tests are non existent for many components
> * unit tests when present have poor coverage
See above.
This also appears to be an issue for a number of container environments.
Has anyone tried working with the Cactus project to get Avalon support
added?
> * unit tests when present and with good coverage are not run (and thus
> "released" code fails to pass them)
Get them put into GUMP.
> * when changes are made the required work of making changes is rarely done
> (involves updating all avalon users of change, gump, build system and
docs).
Propose a CHECKLIST.
> * licenses on 90% of files is invalid
Because of the short license? I posted an sed script to community@ some
weeks ago to help with that process. Be happy to help someone use it, if
they want.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
