blob: 939202d9080c43ff1101d073c53d86ab99819b85 [file] [log] [blame]
<h1>Callisto M5 Status Call (March 3, 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>David Orm (VE)</td>
<td></td>
<td>Sri Doddapaneni</td>
<td></td>
<td>John Duimovich</td>
</tr>
<tr>
<td>Dave Steinberg (EMF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>David Williams</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Doug Gaff</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Doug Schaefer (CDT)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>John Graham (DTP)</td>
<td></td>
<td></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>Rich Gronback (GMF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Scott Lewis</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>
<tr>
<td>Tim Wagner (WTP)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Tyler Thessin (TPTP)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Ward Cunningham</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Wenfeng Li (BIRT)</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>We didn't discuss these items, so they carry forward another week.</p>
<p>ACTION ITEM [David] - will get the Callisto update site(s) in multiple
schemes done today.</p>
<p>ACTION ITEM [David] - post URLs for the update site (multiple schemes) before
Monday morning (and send email to the mailing list)</p>
<p>ACTION ITEM [Richard] - <a href="http://www.eclipse.org/projects/callisto.php?key=2006.02.24"> will update the wiki page with instructions</a></p>
<h2>Apology from Bjorn</h2>
<p>In return, the team asks for lots of free beer at EclipseCon.</p>
<h2>Status By Project</h2>
<ul>
<li>BIRT
<ul>
<li>Milestone build waiting for PMC to vote and then it will be go.</li>
</ul>
</li>
<li>GMF
<ul>
<li>M5 is building all day; will be posted by the end of the day.</li>
</ul>
</li>
<li>TPTP
<ul>
<li>Confirming that the last build is ready to go; have update site ready;
hoping that it will all work by noon</li>
</ul>
</li>
<li>WTP
<ul>
<li>S build transfering to update manager</li>
</ul>
</li>
</ul>
<h2>Update Site</h2>
<p>David talks about update site. Platform doesn't believe that a separate update site for each file
can be reliable enough for this release. So we have to copy the Callisto files to a single directory
on the server. One update site that physically, on the eclipse.org server, has all the feature
jars for all the Callisto projects. Each project should still have your own update sites.</p>
<p>Rich then explains about a nifty command line PDE feature that none of us
knew about (see Help > References > Plug-in Guide > Additional Information > Command Line Interface to Update Manager)
that can be used (by David) to take our existing Callisto site.xml with
references to all the separate update site jars and then &quot;cache&quot; it
all into a new single Callisto update site. This will automatically do what
David was thinking of doing by hand. Great!</p>
<p>David's status: waiting to hear from the four teams. Will look into the mirror command.
Target is that M5 Callisto will be GA approximately Tuesday because we want to make sure that all
projects get a chance to test it first. Target is Monday for this mailing list.</p>
<h2>Installer</h2>
<p>David introduces the idea of a Callisto installer. A small RCP application
that installs the basic Platform and opens the update manager pointing to the
Callisto update site. "Making it easy for volunteers to help".
"A benefit of Callisto is the common download." Everyone on the call will go back to their Board member and re-report back next
Friday as to whether the Board thinks that this (a small, but slick, installer) is a good idea. Tim (WTP) and Wenfeng
(BIRT) discuss the wild popularity of their existing all-in-one downloads.</p>
<blockquote>Subsequent clarification from David: my suggestion for "Callisto Installer" was to be a much less ambitious thing than Yoxos ... maybe "installer" is even the wrong word ... I was thinking of more an RCP app that would be smaller than the Platform feature (30 Megs) and give some user-friendly, automatic "lead in" to the update manager, I would see this Callisto "quickly get started miniature update manager"? to be like a "use once" app, and then future installs, removals, configuration management, etc., to be handled "as usual" by Update Manager or other tools.</blockquote>
<p>ACTION ITEM [All] - Report back from Board member conversations.</p>
<h2>Best Callisto Bugs Contest</h2>
<p>Ward talks about the best bug contest. Questions about "does it have to be Callisto only or more general?"
and &quot;are committers eligible?&quot; We conclude that rewarding WTP
developers for filing WTP bugs is not what this is about, but rewarding WTP
developers for filing great cross-project bugs, say against TPTP, is (a subset
of) what this is about. Non-committers are, of course, also eligible.&nbsp;</p>
<p>Tim and Ward have suggestions for providing suggestions to people about how
to test; scenarios for cross-project testing; installation issues; what it is in
particular that we are looking for. A wiki page will be started (by Ward) about
how testing is going; with suggestions for areas that need more work; here's an
area that looks like a fruitful place for more bugs; etc.</p>
<p>We considered five different ways for developers to signal great bugs to the
PMCs:</p>
<ol>
<li>email to PMC lead</li>
<li>a second bug (a nomination) for each nomination</li>
<li> nomination bug; add each new nomimation as comment</li>
<li>nomination bug via a &quot;depends on&quot; reference</li>
<li>a keyword</li>
</ol>
<p>We decided that a keyword would be the best idea - queries would be easy and
the leads are already overwhelmed with email.</p>
<p>ACTION ITEM [Bjorn, Ward] - finish off the instructions and webpage for this
contest</p>
<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 5, 2006.</i></font></p>