I am asking there to be an official vote and line drawn in the sand that says before version X the only contract that mattered was Framework and everything else was a container feature. Starting with version X Avalon is XYZ.
There was a vote. AF4.2 was released. Excalibur was spun-off. Avalon is moving forward.
IOW, Everything up to Avalon 4.2 is just framework, and Avalon 4.3/5/X on includes framework, meta, and anything else I don't know about.
There is no such thing as Avalon 4.2. There is avalon-framnework-api-4.2. Anything else we don't know about either because it does not exist yet. But what you can be sure if is that a 4.3 will be backward compatible.
So the problem is contractual, community, and branding.
You problem is contractual, community, and branding. Avalon's problems are technical.
Stephen.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
