This is a declaration of what I _know_ is stable and supportable
in Avalon Framework, and what I _know_ is not stable in the framework.
After this, what I am aware of that needs to be addressed.
STABLE
------
Framework interface contracts and usage (needs better docs, though).
(AKA org.apache.avalon.**)
Excalibur Component Management Framework
Excalibur Datasources
Excalibur CLI package
Excalibur Concurrent Lock class (other classes I don't know about).
Excalibur IO FileFilters (the other classes?)
Excalibur Pool SingleThreadedPool implementation
UNSTABLE
--------
Framework interface packages (almost done hopefully)
Excalibur i18n package (not sure if it works, or it's applicability
at this level--unnaware if it is used anywhere).
Excalibur Pool multithreaded pool implementations
Excalibur Thread package (it uses Pool package)
UNSURE
------
Excalibur Collections package
Excalibur Concurrent classes other than Lock
Excalibur IO package (non-filefilter)
ACTIONS TO TAKE:
1) Stabilize packages for org.apache.avalon.** What are the known issues?
2) Stabilize Excalibur Pool and Thread packages
3) Move Excalibur i18n to a whiteboard location (i.e. not in avalonapi.jar)
4) Test all the unsure areas. If stable, we keep, if unstable and not easily
fixed, we move to whiteboard location.
5) Document the compenents and interfaces well (ensuring that the description
is consistent).
Please bring to my attention anything I may have missed. Also, note that I
am more than willing to support the Excalibur DataSources and Component Management
framework since I already do.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
