| [birt-dev] Eclipse BIRT PMC Meeting Minutes - Monday, August 28, 2006 |
Meeting
BIRT PMC, 10am Pacific, Monday, August 28, 2006
Attendees
Wenfeng Li - BIRT PMC Lead - Actuate Corporation (www.actuate.com)
Paul Clenahan - BIRT PMC - Actuate Corporation (www.actuate.com)
Scott Rosenbaum - BIRT PMC - Innovent Solutions (www.innoventsolutions.com)
Larry Liang - BIRT PMC - InetSoft Technology Corporation (www.inetsoft.com)
Minutes
Meeting Logistics
There was no meeting last week, Monday August 21, due to travel schedules.
BIRT 2.1.1 Planning
The BIRT 2.1.1 maintenance release continues to be planned for a September 29, 2006. This will be a coordinated release with a number of other Eclipse projects (see http://wiki.eclipse.org/index.php/Callisto_Coordinated_Maintenance).
Release Candidate build was made available today. Additional show-stopper defects continue to be scheduled for the release, but with the overall rate of change being fairly low.
The development plan for this release can be seen at: http://www.eclipse.org/birt/phoenix/project/project_plan_R2_1_1.php. All items already addressed in the release, or scheduled to be addressed can be found in Bugzilla.
MS Word Emitter Project
The development team have completed the code for the MS Word Emitter and this now needs to go through code review and get checked into CVS. It is to be determined if this is part of the BIRT 2.1.1 download by default, or if it is made available as a separate download.
BIRT 2.2 Planning
The next BIRT major release will be BIRT 2.2 or 3.0 -- with the final feature set determining the release designation.
No change in status for this release. There are a number of initial projects assigned to this release in Bugzilla but we do not have a formal development plan in place yet.
BIRT Project Specifications (BPS), Wiki and Bugzilla
As with previous major releases, we will be creating BIRT Project Specifications (BPS) for the major projects and these will be published using the BIRT Wiki pages (http://wiki.eclipse.org/index.php/BPS) for community review. Feedback will be collected via the corresponding Bugzilla entries for the projects.