> -----Original Message----- > From: Leo Sutic [mailto:[EMAIL PROTECTED] > > Since there is no reasonable way of fixing the underspecification of > the 4.x versions without altering the framework, I think Niclas, > Stephen et al should switch to Avalon *5*, and just start cutting > cruft left, right and center. You know you'll end up with a better > result that way. *And* it will give you the room you need to > experiment.
+1 My suggestion, in simple words: Take the current Avalon-Merlin platform as presented in the current website and label it Avalon 5. This relieves a lot of the current pressure and tensions. Make a place for Avalon 4. Preferably it would be another "product" along side Merlin and the Avalon 5 platform. The Avalon 4 documentation would cover the various documents and aspects mentioned in my earlier email on "Regarding Avalon Framework" We should probably also provide a branch in SVN for Avalon 4 vs Avalon 5. Avalon 4 branch would be stable and the only updates would be for bug fixes. J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
