1. Timeframe for Muse 2.2.
a. Need input from contributors as to optimal release date based
on availability, dependencies, and consuming projects.
b. As always, code freeze should be three weeks prior to release.
2. Initial discussion on content for Muse 2.2.
a. Currently have a number of bugs that Dan and Andrew are working
on.
b. Only 'new feature' right now is support for J2ME. Others?
c. Need to set deadline for new content proposals like we did for
2.1.
3. Tracking our libraries from release to release - how to keep
Axis2/OSGi/etc. material separate for each release while keeping the
install process fairly simple (one script). Andrew and Vinh posted
thoughts on this here:
http://marc.theaimsgroup.com/?t=116669536400001&r=1&w=2
4. Progress of nightly build automation from Andrew.
Dan Jemiolo
IBM Corporation
Research Triangle Park, NC
+++ I'm an engineer. I make slides that people can't read. Sometimes I eat
donuts. +++
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
