blob: 7b99e638c26ffb78f2fa6c306fa0f8a8d0d791b3 [file] [log] [blame]
<h1>Callisto M5 Status Call (March 10, 2006)</h1>
<div align="center">
<center>
<table border="0" cellspacing="3">
<tr>
<td align="center" bgcolor="#CCCCCC"><b>Attending</b></td>
<td align="center"></td>
<td align="center" bgcolor="#CCCCCC"><b>Late</b></td>
<td align="center" >&nbsp;</td>
<td align="center" bgcolor="#CCCCCC"><b>Regrets</b></td>
<td align="center" >&nbsp;</td>
<td align="center" bgcolor="#CCCCCC"><b>Missing</b></td>
</tr>
<tr>
<td>Bjorn Freeman-Benson</td>
<td></td>
<td>Doug Schaefer (CDT)</td>
<td></td>
<td>Doug Gaff</td>
<td></td>
<td>John Duimovich</td>
</tr>
<tr>
<td>Dave Steinberg (EMF)</td>
<td></td>
<td>John Graham (DTP)</td>
<td></td>
<td>Tyler Thessin</td>
<td></td>
<td>David Orm (VE)</td>
</tr>
<tr>
<td>David Williams</td>
<td></td>
<td>Sri Doddapaneni (TPTP)</td>
<td></td>
<td></td>
<td></td>
<td>Ward Cunningham</td>
</tr>
<tr>
<td>Ed Merks</td>
<td></td>
<td>Wenfeng Li (BIRT)</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Kevin Haaland (Platform)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Pascal Rapicault</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Paul Styles</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Rich Gronback (GMF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Tim Wagner (WTP)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Steve Shaw (GEF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</table>
</center>
</div>
<h2>Action Items From Last Week</h2>
<p>ACTION ITEM [Bjorn, Ward] - finish off the instructions and webpage for this
contest <i>- completed <a href="/projects/callisto-files/callisto-bug-contest.php">here</a></i></p>
<p>ACTION ITEM [All] - Report back from Board member conversations. - <i>reports
so far are all positive (i.e., they have no problem with a Callisto installer-lite)
and from Actuate, BEA, Intel, and Sybase. (Bjorn asks: did I miss anyone?)</i></p>
<p>ACTION ITEM [Richard] - update wiki with instructions - <i>completed <a href="http://wiki.eclipse.org/index.php/Callisto_Build_and_Update_Tips_and_Tricks">here</a></i></p>
<h2>M5 Stable Enough To Declare</h2>
<p>The team agreed that Callisto M5 and the update manager process is
&quot;stable enough so that early adopters can help with testing and finding the
worst problems&quot;. We are still concerned with the update manager's ability
to handle this kind of load and we are concerned with the infrastructure's
ability to handle this kind of load. The update manager introduces additional
traffic on the infrastructure due to the fact that it doesn't just download
everything in a single blob: more round trips in tradeoff for (if not everyone
installs all the features) potentially few bytes. Given that infrastructure
caused us over a week of grief with 403 errors, how will it stand up to the load
when our larger community starts downloading?</p>
<p>ACTION ITEM [Bjorn] - announce Callisto M5 to foundation newsgroup, dev lists
of each of the ten projects, blog.</p>
<h2>Callisto CVS Components</h2>
<p>David suggested, and everyone agreed, that we should have a Callisto CVS
component for storing the rel-eng type files and scripts that he's been
building. Easily said and done, it now exists here: /cvsroot/callisto</p>
<h2>After Callisto - Integration?</h2>
<p>We discussed whether we should have a single Callisto update site for
maintenance releases. The real question is whether we want to commit to
maintaining synchronized releases, i.e., synchronized maintenance releases,
after Callisto. We made a number of decisions:</p>
<ul>
<li>We are going to do this (simultaneous release) once and then look back and
see how well it worked and whether we want to do it again.</li>
<li>We are not going to change the Callisto update site after it has been
released (gone golden).</li>
<li>We are planning to try to synchronize our point releases, but we are not
guaranteeing to do so or guaranteeing a particular schedule.</li>
<li>We won't take any steps that would preclude ourselves from doing
synchronized maintenance releases in the future.
<ul>
<li>If project X is using internal APIs of project Y, then project X needs
to define dependencies on the exact versions of the project Y plug-ins
so that any maintenance releases of project Y do not break project X.</li>
</ul>
</li>
</ul>
<h2>Installer</h2>
<p>Everyone seems ok with this, but we concluded that we would see how well the
update manager worked before we allocated any effort to building an installer.
Another option we talked about it (if the update manager fails) is to create a
giant zip of all the files.</p>
<h2>Daryl Taft</h2>
<p>Daryl Taft has proposed listening in to all our calls and writing an article
about how we built Callisto for publication around the Callisto main release.
While we all got a bit shy about our words coming back to haunt us, we
acknowledged that we are open source and try to be open in everything we do and
so we said ok.</p>
<h2>RC0 Process</h2>
<p>We started talking about each project's plans and risks for RC0, but decided
to postpone until the face-to-face next week:</p>
<ol>
<li>What sort of ramp down policy is in effect?</li>
<li>What bugs are being worked on?</li>
<li>What cross-project testing commitments are being made?</li>
<li>What risks are there for the RC0 dates?</li>
</ol>
<h2>EclipseCon Meeting</h2>
<p>The Planning Council will meet at EclipseCon on Sunday from 6pm-8pm. Some
sort of food will be provided.</p>
<p><font size=-1><i>Minutes posted by Bjorn Freeman-Benson March 11, 2006.</i></font></p>