Meeting Date:
6/2/06 11:00 a.m. EDT
Attendees:
Sal Campana
Glen Everett
Joel Hawkins
Dan Jemiolo
Bill Reichardt
Mark Weitzel
Topics:
1. Requirements for publishing a development release of the new
code within a three-week time frame.
2. Build and release: tools, processes, and considerations.
3. Feasibility of six-week development/release cycle after first
development release.
News & Decisions:
0. We need to get the code and build up and running so that
everyone can take a serious look at it! We would like to have a
development release (0.9) for "Muse 2" in three weeks.
1. Joel and Glen work on Project Corona at eclipse.org and are
interested in both contributing the OSGi support for Muse 2.0. They have
taken the code in JIRA and made some good progress on this so far.
2. The current Muse project uses Maven for the build process. The
team has no Maven "expert", and Dan hasn't used it before. In order to get
things up and running as quickly as possible, Dan will learn how the
current Maven build works and modify it to generate targets based on the
new code. This work can be started before commit access is granted.
2a. We may need to use additional scripting in the Maven build in
order to create the bundle-based packages that are needed for OSGi
support. Sal and Joel discussed previously-discovered issues and how they
can be addressed. It was agreed that this would not be a major issue to
resolve.
3. We need to create a new SVN branch for the new code, but the
team is unsure what the proper protocol is for such a move. There was
general agreement that we could create a branch with the current code
(which combined WSRF, Pubscribe, and Muse into one), then replace the
contents of the trunk using the new code and create a branch for that.
There wa also agreement that Sal should check with the appropriate Apache
contacts to make sure this is the right thing to do before we do it. :)
4. There was agreement on a six-week code-test-release cycle
following the initial development (0.9) release in three weeks.
Action Items:
1. Dan needs to install Maven and make sure he can perform the
current build. He will then start modifying it in a way that will work for
the new code and send updates so people can comment on or correct his
direction.
2. Sal will continue with the admin work needed to get commit
access/account for Dan.
3. Sal will check to make sure our plan for SVN modifications is
appropriate.
If you have any questions or clarifications about these minutes, please
send them along!
Thanks,
Dan
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]
