| <?xml version="1.0" encoding="ISO-8859-1" ?> |
| <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <title>WTP PMC Minutes for March 22, 2005 Conference Call</title> |
| </head> |
| <body |
| alink="#ff0000" |
| bgcolor="#ffffff" |
| link="#0000ee" |
| text="#000000" |
| vlink="#551a8b"> |
| <table |
| border="0" |
| cellpadding="2" |
| cellspacing="5" |
| width="100%"> |
| <tbody> |
| <tr> |
| <td |
| colspan="2" |
| align="left" |
| bgcolor="#0080c0" |
| valign="top"><b> <font |
| color="#ffffff" |
| face="Arial,Helvetica">PMC Conference Call - March 22, 2005</font></b></td> |
| </tr> |
| </tbody> |
| </table> |
| <table |
| border="0" |
| cellpadding="2" |
| cellspacing="5" |
| width="100%"> |
| <tbody> |
| <tr> |
| <td> |
| <h2>WTP PMC Minutes for March 22, 2005 Conference Call</h2> |
| <p>Attending: Tim Wagner [TW], Arthur Ryman [AR], David Williams [DW], Dominique De Vito [DV], Jochen |
| Krause [JK], Naci Dai [ND], Bjorn Freeman-Benson [BB], Christophe Ney [CN]</p> |
| <p>Others: Lawrence Mandel (representing WTP community) [LM]</p> |
| <h2>Procedural matters</h2> |
| <ul> |
| <li>TW: Reminder that private mailing list (wtp-pmc@objectweb.org) has been decommissioned and all |
| PMC members and other interested parties should subscribe to the Eclipse-hosted one |
| (wtp-pmc@eclipse.org).</li> |
| <li>AR: Requested that EMO investigate IRC server for telecon use.</li> |
| </ul> |
| <h2>Community [LM]</h2> |
| <ul> |
| <li>OOPSLA submissions for tutorial and panel completed</li> |
| <li>JK and DV also presenting at conferences; will update Lawrence with info</li> |
| <li>Messaging: no response yet from WTP community; LM requested that PMC members appeal to their |
| respective organizations for support in writing articles and communicating WTP info; EclipseCorner in |
| particular is easy to publish to and eager for material</li> |
| <li>TW: BEA eWorld, dev2dev interview, and JavaOne conference are likely candidates for WTP |
| presentations; more as the event dates/agendas crystallize</li> |
| <li>CN: ObjectWeb hosting conference in Viet Nam at which WTP information will be presented</li> |
| <li>WTP help system initial content should be available by next week (delayed from previous |
| estimate); currently working towards stable local builds</li> |
| </ul> |
| <h2>Documentation Strategy</h2> |
| <ul> |
| <li>PMC discussed the likelihood of a lag between code GA and documentation readiness, especially |
| in light of the limited resources and the size of the initial documentation content drop from IBM. If we |
| ship in July, a September doc release, with subsequent quarterly updates, might be a tractable schedule. |
| Expect to use professional writers (devs may author initial content or edit subsequently). Initial code |
| release will contain samples, JavaDocs, and anything else thats ready at that point.</li> |
| <li>Documentation will have a separate build process/schedule. LM/AR to pursue offline.</li> |
| <li>AR: IBM has product documentation resources that will contribute to this effort</li> |
| <li>TW: BEA probably in similar state; some fraction of a doc resource likely available to help |
| post (BEAs) 9.0 delivery</li> |
| </ul> |
| [PMC members only for the remaining portion of the meeting] |
| <h2>Requirements Group Report [JK]</h2> |
| <ul> |
| <li>Requirements group composition: |
| <ul> |
| <li>Paul Meijer (BEA)</li> |
| <li>Todd Williams (Genuitec)</li> |
| <li>Arthur Ryman (IBM)</li> |
| <li>Jochen Krause (Innoopract, chair)</li> |
| <li>Ivelin Ivanov (JBoss)</li> |
| </ul> |
| </li> |
| <li>First meeting will follow next weeks PMC call</li> |
| <li>Version numbering PMC discussed merits of next version being 1.1 (historical consistency, |
| description of maturity of project) versus 3.2 (alignment with platform, less confusion for users). |
| Tabled final decision pending feedback from Eclipse Councils next month.</li> |
| </ul> |
| <h2>Architecture Group Report [DW]</h2> |
| <ul> |
| <li>Several new bugs posted [see query string in last weeks minutes tw]</li> |
| <li>Thursday call agenda: Browser resolution (move to platform?), tabbed property page (same |
| question)</li> |
| <li>TW: What role is Architecture Group playing in API review? DW: Focusing on WTP vs. platform and |
| cross component issues as detected by themselves, component leads, or members of the community.</li> |
| <li>TW: Suggested that a community review of the APIs in the form of 1-2 hour presentations by each |
| component lead would be a forum for API commentary. Architecture Group could help structure the review, |
| but the community at large would own the outcome. AR noted that timeframe must be post M4 to allow API |
| definition process to complete.</li> |
| </ul> |
| <h2>Disk Quota/Build Issues [AR]</h2> |
| <ul> |
| <li>Problem is not so much disk quota on our main server as the load we place on mirrors; if we |
| trim down the nightly size, that will have the biggest impact</li> |
| <li>Three suggestions |
| <ol> |
| <li>Dont retain nightly builds beyond the next integration build</li> |
| <li>Dont publish non-SDK bundle in nightlies (theyre only for dev use)</li> |
| <li>Dont publish WST-only bundle in nightlies (same reason)</li> |
| </ol> |
| PMC resolved to adopt all three changes to the process, and that warmup (pre-final) I-builds need not |
| be kept after the next successful I-build.</li> |
| </ul> |
| <h2>Integration Builds [ND]</h2> |
| <ul> |
| <li>Platform insists that test failure implies the result is not an I-build; weve lacked that |
| level of quality in our I-builds</li> |
| <li>Our previous milestone releases have been stressful because of accumulated test failure debt</li> |
| <li>Current (updated) process is to attempt the I-build on Tuesday, focus on build or test failures |
| midweek attempting to produce a successful build on Thursday. Expectation is that there are no large |
| changes between Tuesday and Thursday; changes can be released to head, just not included in the I-build |
| candidate.</li> |
| <li>Biggest remaining problem is getting people to focus on tests; will now <em>require</em> tests |
| to pass to release the I-build (otherwise we fail for the week and try again the following week rather |
| than posting the failure).</li> |
| <li>[AR] For m4 we have two buckets: real tests, and API tests that do not yet have backing |
| implementation and will therefore fail. For the duration of m4, we need to manually differentiate in |
| declaring the I-build green.</li> |
| <li>[ND] Also, Linux machine should be up this weekend, so we will start having parallel builds on |
| Linux as well as Windows.</li> |
| </ul> |
| <h2>API Review</h2> |
| <ul> |
| <li>PMC reviewed initial API statistics; will track component convergence over time to help drive |
| process.</li> |
| </ul> |
| <h2>RDB / DTP Issues [AR]</h2> |
| Arthur posted minutes of previous meeting to mailing list. Components would likely move in August (pending |
| proposal approval); still considering whether to rename them in advance to limit later churn on other WTP |
| components that are downstream. |
| <h2>Action Items:</h2> |
| <ul> |
| <li>[JK/DV/CN] update Lawrence with info on upcoming conference presentations of WTP info</li> |
| <li>[TW/DW] work on scheduling API review by component leads</li> |
| <li>[ND] update build scripts based on the Quota resolutions (see above)</li> |
| <li>[ND] update build page with process change (test pass requirement) for I-builds</li> |
| <li>[AR] ask Jeffrey to add time series tracking to API statistics pages so we can track trends at |
| the component level</li> |
| </ul> |
| <small>Minutes taken by Tim Wagner, March 22, 2005</small></td> |
| </tr> |
| <tr> |
| <td> </td> |
| </tr> |
| </tbody> |
| </table> |
| </body> |
| </html> |