> -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED]
> For step 1, quick beta release of Merlin > ---------------------------------------- > > What loose ends need to be tied up before we can do this? Do we need to have a 'beta' release of Avalon-meta before hand? > For step 2, which features need to be incorporated in Merlin? > ------------------------------------------------------------- > > * Embedding Fortress containers > * Configuration validation > * Support for Pheonix's Environment.xml (security policies, logging, etc.) > * Support for the @mx-* tags > * Daemon support (i.e. running as a Windows service or Unix daemon) > * Phoenix Client support (i.e. the BlockContext, et. al.) > * Support for Phoenix Assembly.xml files > * SAR support > > Anything I am missing? While this may seem like extras, I think good JMX and JNDI exporting support is vital. The emergence of the Geronimo project only emphasizes this. Also, as Leo mentioned, getting pico/nano support would be a nice plus, but it probably shouldn't be a blocker to getting Merlin out. Also we should make sure good documentation is available. I'd love to work with Stephan (and anyone else) in putting together a great Avalon beginners tutorial. Finally, I wish we had JIRA available to keep track of these issues for release! I suppose we could start using the Forrest status file in the meantime. > We may want to do multiple beta releases as we add new functionality so > that > we can get feedback from users. +1 > For step 3, what "exit" criteria do we need? > -------------------------------------------- > > Can we create the exit criteria in the form of JUnit tests? Sounds good to me. Berin, I think this is an excellent solution. I'm glad to see some progress being made. I'll help in any way possible. Thanks, jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
