On Tuesday 05 August 2003 02:42, Stephen McConnell wrote: > >BTW, after a first look of many hours, Merlin is not that easy to > > mastering. > > Lies, lies, damnable lies!
LOL > Well, actually, it should be drop dead simple but you know how it is, > users keep getting in the way, comming up with things thay want to do to > which above and beyond the call of duty. I mean - what can you do? Agree, it's not easy. Especially when you have to deal with many notions (distinct from Merlin) such as Maven, IoC, etc. What about writting an Oreilly Book? AFAIR Oreilly is open on any technoid subject that could sale more than x books (having x not so high) "Avalon Practice with Merlin" :) > >Would it be possible to have a burnout-session/beer with one toplevel guru > >floating around, to push an openim release based on Merlin? > > Absolutely. Let's do it! Great! > As to your question of "inside or outside of Avalon" - that's an > interesting one. If Merlin stays within Avalon it seems that it will be > disruptive. But I figure that this is better than a move outside of > Avalon. Personally I think Merlin should have had a release here in > Avalon about a year ago. Maybe I should just post a vote and take it > from there. My opinion is that we (the developpers outside the inner circle) need official frequent stable releases (generally speeking), and Merlin cannot stay in sandbox for years. CVS update is cool, but time consuming if you are not working on avalon mainstream stuff. So maybe someone could push a 2.x release branch outside Avalon, and Merlin team could try to work with avalon community 'hand in hand' (lol) to converge with 3.0 (and if Merlin3 can maintain ascendant compatibity, it should be great). > One of the things that I see as slowing things down is assumption about > what a release means. Personally I want a Merlin release to be an active > vibrant rolling beta process with a stable component contract combined > with a volatile container contract until such time that we feel we have > cracked the equation. I.e. moving away from: > > [a bunch of monks mumbling in monotone] <snip mode="funny"/> > Merlin 2.1 is fine as it is. > That's what you end with using the current > CVS and Merlin command line. Its ready to go, validated against all of > the cornerstone components, James, a bunch of my own experiments, and a > number of external projects (a couple of which have successfully pushed > Merlin well beyond the things I’ve been playing with). So let push him out somewhere. If big players here are ok to have an official Merlin 2 within avalon, this could be nice, otherwise, join the darkside for a while. And could we keep dithyrambic rhetorics based on Merlin 3.0 and "community convergence" in this mailinglist. No? > Merlin 3.0 is a process that is starting to emerge - its shaping up to > be about (a) refactoring of the assembly system, (b) separating out a > management model we can easily handle things with JMX, (c) improving the > APIs exposed to container extensions, (d) setting the groundwork for > distribution and federation, while (d) making sure that we having a good > time! Sounds mirific, delirious, wonderful (MDW). Regards, --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
