blob: 3ef2257f27209070142b1e825622770f16095e5a [file] [log] [blame]
<?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 May 3, 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 - May 3, 2005</font></b></td>
</tr>
</tbody>
</table>
<table
border="0"
cellpadding="2"
cellspacing="5"
width="100%">
<tbody>
<tr>
<td>
<p>WTP PMC Minutes for May 3, 2005 Conference Call</p>
Attending: Tim Wagner [TW], David Williams [DW], Arthur Ryman [AR], Dominique De Vito [DD], Naci Dai [ND]
<h1>WTP PMC Minutes for May 3, 2005 Conference Call</h1>
<h2>No procedural matters</h2>
<h2>Community Update [LM]</h2>
<ul>
<li>Just over 8K downloads of M4 to date</li>
<li>Working with Ian Skerrett (EMO) and Pieter Humphrey (BEA) on WTP 1.0 press release</li>
<li>Articles in technical journals need to be written to build awareness of WTP; see Lawrence or
Ian to participate</li>
<li>Arthur, Jochen writing for JDJ</li>
</ul>
<h2>M4 API and Release Debrief</h2>
<ul>
<li>All APIs met exit criteria except the (EMF-generated) J2EE model; dynamic tracing coverage of
that is now over 50%, but we will still likely have a testing shortfall. Mitigation: Early in M5, close
on 100% coverage for this component.</li>
<li>API violations: Our API violates its own requirements (e.g., return types that are not in the
API). Need to address this, including defining exactly what constitutes a violation (subclassing non-API
classes/interfaces?).</li>
<li>[AR] Suggest starting shutdown sequence a week early to increase M5 ship date reliability. Need
to limit destabilizing changes in shutdown sequence; a lightweight approval process may need to be in
place for M5, which will serve as a rehearsal for GA convergence.</li>
<li>[ND] I-builds not getting to sufficient quality; creates drag on M-builds. May have a better
chance with M5 since APIs are in place. Some tutorials/examples out of date with respect to M4 codeline.
(Lawrence Mandel is organizing the effort to correct them.)</li>
</ul>
<h2>Date And Release Changes</h2>
<ul>
<li>M5 moved to 7/1 to enable sufficient time for development and convergence.</li>
<li>PMC approved requirements group provision of a Dec. 15, 2005 hardening release plan (to be
numbered 1.1)</li>
</ul>
<h2>No Architecture Group Report this week</h2>
<h2>No Requirements Group Report this week</h2>
<h2>Performance Testing Server Support</h2>
<ul>
<li>Need JSP and Derby on server to enable WTP performance testing</li>
<li>PMC approved making request of the EMO</li>
</ul>
<h2>Action Items</h2>
<ul>
<li>TW: work with Paul Meijer on Dr. Dobbs or other WTP article</li>
<li>AR: additional detail around performance testing infrastructure requests</li>
<li>AR: conversation with Roel Stalman regarding Oracle's EJB 3.0 plans and future integration with
WTP</li>
<li>TW: conversation with Steve Todd regarding Borland's use of WTP and possible seat on WTP
requirements group</li>
</ul>
<small>Minutes taken by Tim Wagner, May 3, 2005</small></td>
</tr>
<tr>
<td>&#160;</td>
</tr>
</tbody>
</table>
</body>
</html>