> From: Paul Hammant [mailto:[EMAIL PROTECTED]] > > > <wisdom/> > > Are we all on board? > > Go for it. > > Draw up a list of things that need to be achieved in the run > up to Xmas, and we'll see what it > looks like...
:) As I said, we need to address Priority #1 sooner than later. We are a top level project in Apache, so we need our charter and our bylaws. As to Priority #2: It seems that the majority of us (if not all of us) want to work on one unified container. I posted a plan of attack for that before Thanksgiving break. What we need to discuss is if we are working on an Avalon 4.1 compliant container, or an Avalon 5 container and the associated contracts. I highly recommend that new development is just that--new. It needs to be a fresh start both technically and for us as a community. It also means that while we are working on Avalon 5, we are supporting, maintaining, and releasing our existing containers. Yes, both Merlin and Fortress are Avalon 4.1 compliant, as are Phoenix and ECM. The fact is that we have existing users and existing projects. The fact that they are so different speaks to both the flexibility and the lack of agreement we have had in the past. As we work toward the new Container and the new Avalon we have the one critical piece we didn't have: confidence that a component written for any Avalon container should work the same no matter what. So the critical question is do we clean the slate (leveraging our knowledge of what we have now) to build afresh, or do we continue with what we have? The last we talked about it, we wanted Avalon 5 to address better the container/component contracts more than the simple lifecycle. I think now would be the opportunity to to do just that. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
