Meeting Date:
1/4/07 11:00 a.m. EST
Attendees:
Barry Atkins
Andrew Eberbach
Joel Hawkins
Dan Jemiolo
Balan Subramanian
Topics:
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.
News & Decisions:
1. Timeframe for Muse 2.2 is as follows:
a. Feature freeze (in JIRA): Thursday, January 11th
b. Code freeze: Thursday, March 1st
c. Vote: Monday, March 19th
d. Release: Friday, March 23rd
2. J2ME support will be the major new feature for 2.2.
a. Barry will be working on this - had Muse samples from 2.1
builds running on J2ME, expects to have it running on 2.2 builds very
shortly.
b. Joel will help Barry with packaging of Equinox/J2ME
dependencies.
c. We need to package the JDK code that is not in J2ME and could
not be removed/refactored from the code base. This code will come from
Apache Harmony, and we will not include it as part of the codebase - it
will be a common library that is available as part of the install process.
This is the safest option from a legal standpoint.
3. We will put into effect Andrew's plan (see above link) to versioning
the platform dependencies that users download.
a. Joel also suggested that for the future, we start a discussion
on Apache's general-webservices about creating official OSGi packages for
all of the Apache WS projects; this would free us from having to do it and
would provide a more guaranteed/attractive way to get Apache WS code for
OSGi. We could then download all of our dependencies from independent
sites and not have to maintain them ourselves.
4. Andrew is very close to completing the automation of timestamped
nightly builds.
Action Items:
1. Dan and Andrew are working on JIRA bugs, Barry is working on J2ME
support.
2. Dan will find out how Muse can get a section of the Apache WS Wiki (if
it doesn't already have one) so that we can use it for discussing future
releases and features.
3. Balan will ask IBMers interested in J2ME support to participate in
community and help us test this code.
If you have any questions or clarifications about these minutes, please
send them along!
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]
