> -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Monday, July 12, 2004 2:45 PM > To: Avalon Developers List > Subject: Re: [PROPOSAL] Avalon 5 > > Farr, Aaron wrote: > > > Basic Plan > > ========== > > Label the current Avalon-Merlin platform as presented in > the current > > website (specifically the 'specification section') as Avalon 5. > > > > Present Avalon 4 as a separate "product" which would include: the > > Avalon-Framework jars, javadocs, and related documentation. An SVN > > branch will be created that will be considered STABLE and will only > > accept bug fixes. > > A few days ago, I outlined a 'continuum' of evolution of AF4 > into the Avalon 5. > > The only reaction to that was "has this been discussed", and > I took that as "sounds reasonable to everyone, let's work on that". > > I see the whole flamefest this time, being a big > mis-communication, assumptions and scracthing of old wounds. > > AF4 has been the term I learned, and not Avalon 4. I think > AF4 should evolve prior to an Avalon 5. An abrupt jump now > will mainly constitute a fork, which is not good for anyone. > > AF4.2 has no fundamental change that Berin, Leo and other > container authors should have a problem with. > The changes I would like to see in 4.3 (mainly deprecations) > will probably also be considered reasonable. > Introduction of an Availability contract prior to Avalon 5, > is perhaps more controversial, but could be handled amicably, > and if the AF4 container authors are not Ok with it, it will > become a separate spec from AF4, and marked Avalon Availability 1.0. > > Then we collect the entire suite, and create Avalon 5. > > This is IMO a much more 'small steps' and evolutionary, than > making a break at this time, just because of political reasons. >
+1 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
