blob: 12290480b1c307392d1fe4901db67ae5d333dc92 [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 November 29, 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 - November 29, 2005</font></b></td>
</tr>
</tbody>
</table>
<table
border="0"
cellpadding="2"
cellspacing="5"
width="100%">
<tbody>
<tr>
<td>Attending: Tim Wagner [TW], Jochen Krause [JK], Arthur Ryman [AR] David Williams [DW], Lawrence
Mandel [LM], Raghunathan Srinivasan [RS], Christophe Ney [CN] <!--PMC MEMBERS NOT PRESENT ON THIS CALL:
Naci Dai [ND],
-->
<h1>WTP PMC Minutes for November 29, 2005 Conference Call</h1>
<h2>Community Update [LM]</h2>
<ul>
<li>1.0 rollout
<ul>
<li>Tutorials need to be updated / corrected for 1.0</li>
<li>Blogging by WTP members</li>
<li>Blogging by 3rd parties (will need to inform/remind)</li>
<li>Press release (driven by EMO)</li>
<li>Documentation placed online and searchable by Google</li>
<li>Explore links from main and download page</li>
<li>Arthur created a "FreshMeat" entry for M9 to garner additional awareness of our tools (in
review stage)</li>
<li>Should also plan for Slashdot article</li>
<li>EclipseZone interview</li>
</ul>
</li>
<li>Project Phoenix feedback solicited; anyone who has spare cycles, please feel free to comment on
the content, presentation, and toolset.</li>
</ul>
<h2>Emerging API Migration/Support Policy</h2>
<ul>
<li>Summary by Arthur of non-API support policy proposal (see agenda); goal is to provide best
level of support to adopters that we can. Focus is primarily on 1.0 - 1.5 transition, although even post
1.5 there will be ongoing API evolution issues for adopters to worry about.</li>
<li>Result depends in large part on community engagement; usage reports will be helpful in driving
WTP activities.</li>
<li>Need to ensure that we don't turn this into a mechanism for exposing any arbitrary internal
methods into lifetime commitments.</li>
</ul>
<h2>1.0 Status</h2>
<ul>
<li>Large backlog of bugs, documentation, and JUnit testing going on</li>
<li>Initial RC will take place this week as planned, although there will still be some areas with
insufficient tests</li>
<li>Will solicit P2 review from devs via mailing list (as well as remind people of endgame plan)</li>
</ul>
<h2>Requirements Update</h2>
<ul>
<li>No wiki input yet.</li>
<li>Planning requirements discussion planned for 12/15 status call.</li>
</ul>
<h2>Calisto Update</h2>
<ul>
<li>David reviewed bugs; doesn't look bad, but we cannot commit to making the M4 train due to
conflict with 1.0.</li>
</ul>
<h2>JSF Update</h2>
<ul>
<li>Milestone 1 demo planned for next week.</li>
<li>Build issues getting resolved; progress on feature definition.</li>
<li>Bugzilla organization fixed.</li>
</ul>
<h2>Action Items</h2>
<ul>
<li>[TW] send out clarified end game</li>
<li>[AR] send note to devs regarding P2 status (for RC1 production)</li>
</ul>
<small>Minutes taken by Tim Wagner, November 29, 2005</small></td>
</tr>
</tbody>
</table>
</body>
</html>