I would like to propose that we put some priorities in place.
On our release agenda is Avalon framework 4.1.4, logkit 1.2,
excalibur packages: thread 1.1; sourceresolve 1.0;
configuration 1.0; xmlutil 1.0; store 1.0, cornerstone
packages: threads 1.0; connection 1.0; datasources 1.0;
masterstore 1.0; scheduler 1.0; sockets 1.0 threads 1.0.
If we throw into the equation the potential release of
Fortress we also need to address release of the avalon-sandbox
lifecycle package and the instrument package. Phoenix release
is already out but used non-released code - excalibur
configuration, loader and extension.
Throw into this equation the fact that our current Cornerstone
repository (used by James and Cocoon) has changed at interface and
implementation levels and that every indication from Gump tells us
we have a broken product. Also keep in mind that Cocoon is using the
source, component, xml, store, datasource, pool, testcase, util,
instrument, collections (and possibly other packages) some of which
we have never release.
My proposal is this:
No new release proposals until the current Avalon in-use
excalibur and cornerstone products are finalized,
validated, properly released, and synchronized with
Cocoon and James.
A.K.A - Lets put our priority towards getting Avalon in shape for
our users based on what they are doing today. From that platform
we can move ahead.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
