Berin Loritsch wrote:
To me, the merging of Avalon and Merlin has now lost all traces of what is identifiably Avalon. This is not only a crying shame, but in complete disregard of its roots.
And it is hard to find references in Windows XP about MSDOS as well :o)
But let's put the blame where blame is due;
I.e. The current 'active' group of Avalon developers are Merlin-proponents. We made a presentation to the ASF Board that it was in the overall interest of Avalon that Merlin was broken out and we moved to a TLP.
The Board decided the opposite and made the (unquoted) remark; Avalon voted for a Single Unified Platform, so go ahead and make it happen.
The Board, otoh, decided it was in the best interest of legacy piece, at that time homed at Avalon, to be given a TLP for future development and support of existing applications.
Personally, I think the Board should have opted for the other way around, and I think this current debate is a backlash against the Board's decision, and those who influenced(!) the Board to make such decision. I just live with the interpretation of the decision.
The current definition of what makes Avalon components a component is far more than just framework anymore--so you really need to make it Avalon 5.0 and get rid of deprecated cruft. Just do it, because you have already made Avalon 4.x incompatible.
I recommend still offering Avalon 4.x as a product, and redefining the current slab of products as Avalon 5. That would at least represent reality.
I totally agree with you here. I and Stephen will sure start an official move towards Avalon 5 (note no framework).
Meanwhile, I expect that any incompatibilities in AF4.2 that are genuine (instead of FUD) are reported and we try to deal with it.
Cheers Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
