Google Git
Sign in
eclipse / www.eclipse.org / eclipse / 283e5aa56519b7305d9800532d37435bbb478daf / . / development / freeze_plan_3.2.html
blob: d1f7ecd85bae3e5bda8523e5d700aa18f2323df0 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Eclipse 3.2 Endgame Plan</title>
<link href="../default_style.css" rel="stylesheet">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="Microsoft FrontPage 4.0" name="GENERATOR">
<meta name="ProgId" content="FrontPage.Editor.Document">
</head>
<body text="#000000" vlink="#551a8b" alink="#ff0000" link="#0000ee" bgcolor="#ffffff">
<table cellspacing="5" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td align="left" width="80%">
<p><font class="indextop">Eclipse 3.2<br>
Endgame Plan</font><br>
<font class="indexsub">Updated frequently to reflect current status</font></p>
</td>
<td width="20%"><img src="images/howto_banner.jpg" align="center" width="272" height="111"></td>
</tr>
</tbody>
</table>
<table cellspacing="5" cellpadding="2" width="103%" border="0">
<tbody>
<tr>
<td valign="top" align="left" bgcolor="#0080c0" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Status</font></b></td>
</tr>
<tr>
<td valign="top" align="right"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td> <p><b><font color="#ff0000">May 26, 2006, Status: 3.2RC6 now available. RC7 build is Friday, June 2 at 00:10 EST.</font></b></p>
</td>
</tr>
<tr>
<td valign="top" align="left" bgcolor="#0080c0" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Detailed
Timeline</font></b></td>
</tr>
<tr>
<td valign="top" align="left" colspan="2">
<table border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td align="right" height="18"><b>April 2006</b>&nbsp;</td>
<td height="18"><img src="images/tbar_l.gif" width="24" height="18"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">3</td>
<td align="right" height="18">Mon 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Transition to fix and polish mode</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#Transition"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">details</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">13</td>
<td align="right" height="18">Thu 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 1 build</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC1"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="10"></td>
<td align="center" height="10"><img src="images/gray.gif" width="2" height="10"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">17</td>
<td align="right" height="18">Tues 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Start fix pass</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#FixPassAfterRC1"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">rules</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="30"></td>
<td align="center" height="30"><img src="images/gray.gif" width="2" height="30"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">25</td>
<td align="right" height="18">Tues 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Full day test pass to stabilize for RC2</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#TestPassBeforeRC2"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">details</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="30"></td>
<td align="center" height="30"><img src="images/gray.gif" width="2" height="30"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">28</td>
<td align="right" height="18">Fri 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 2 build</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC2"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td align="right" height="18"><b>May 2006</b>&nbsp;</td>
<td height="18"><img src="images/tbar_l.gif" width="24" height="18"></td>
</tr>
<tr>
<td height="10"></td>
<td align="center" height="10"><img src="images/gray.gif" width="2" height="10"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">1</td>
<td align="right" height="18">Mon 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Start 2-day test pass against RC2</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#TestPassUsingRC2"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">details</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="10"></td>
<td align="center" height="10"><img src="images/gray.gif" width="2" height="10"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">3</td>
<td align="right" height="18">Wed 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Start fix pass</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#FixPassAfterRC2"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">rules</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="15"></td>
<td align="center" height="15"><img src="images/gray.gif" width="2" height="15"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">5</td>
<td align="right" height="18">Fri 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 3 build</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC3"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="10"></td>
<td align="center" height="10"><img src="images/gray.gif" width="2" height="10"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">8</td>
<td align="right" height="18">&nbsp;&nbsp;&nbsp;Mon 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>All-day test pass against RC3</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#TestPassUsingRC3"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">details</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">9</td>
<td align="right" height="18">Tue 08:00 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Start fix pass</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#FixPassAfterRC3"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">rules</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">12</td>
<td align="right" height="18">Fri 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 4 build</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC4"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
<td align="right" height="18"></td>
<td align="right" height="18"></td>
<td height="18">&nbsp;&nbsp;<b>Post RC4 builds will be run to meet translation,</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
<td align="right" height="18"></td>
<td align="right" height="18"></td>
<td height="18">&nbsp;&nbsp;<b>documentation and Callisto goals.</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">19</td>
<td align="right" height="18">Fri 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 5 build</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC5"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">26</td>
<td align="right" height="18">Fri 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 6 build</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC6"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="18"></td>
<td align="center" height="18"><img src="images/gray.gif" width="2" height="18"></td>
</tr>
<tr>
<td align="right" height="18"><b>June 2006</b>&nbsp;</td>
<td height="18"><img src="images/tbar_l.gif" width="24" height="18"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18">2</td>
<td align="right" height="18">Fri 00:10 EDT</td>
<td height="18">&nbsp;&nbsp;<b>Release Candidate 7 build</b></td>
<td height="18">&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#RC7"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">goals</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="20"></td>
<td align="center" height="20"><img src="images/gray.gif" width="2" height="20"></td>
</tr>
<tr>
<td height="18"></td>
<td height="18"><img src="images/tbar_r.gif" width="24" height="18"></td>
<td align="right" height="18"></td>
<td align="right" height="18"></td>
<td height="18">&nbsp;&nbsp;<b>Release 3.2 available</b></td>
<td height="18">&nbsp;&nbsp;</td>
<td height="18">&nbsp;&nbsp;<b><a href="#Release3.2"><img src="images/jump_in_black.gif" border="0" hspace="3" width="12" height="10"><font color="#00aa00">details</font></a></b></td>
<td height="18">&nbsp;&nbsp;</td>
</tr>
</table>
</td>
</tr>
<tr>
<td valign="top" align="left" bgcolor="#0080c0" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Useful
Links</font></b></td>
</tr>
<tr>
<td valign="top" align="right"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td>
<p><a href="component_test_plans_3.2.html">Component Test Plans</a> - info
on how to test each of the components.</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td>
<p><a href="http://www.eclipse.org/eclipse/platform-releng/3.2-endgame-buildschedule.html">3.2 Endgame Build
Schedule</a> - details on build times.</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td>
<p><a href="release_checklist_3.2.html">Eclipse Release Checklist</a> -
lists various things that need to be checked before each release.</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td>
<p><a href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html">Eclipse
Project 3.2 Plan</a></p>
</td>
</tr>
<tr>
<td valign="top" align="left" bgcolor="#0080c0" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">What
is the game plan?</font></b></td>
</tr>
<tr>
<td valign="top" align="right" width="2%"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td width="98%">
<p>The Eclipse 3.2 release endgame involves a sequence of test/fix
passes leading to the official 3.2 release. Even more than at other
times, we welcome all the help we can get with testing and fixing the
various Eclipse release candidates. To participate effectively everyone
needs to track this schedule closely so that we end up testing the
latest release candidate and entering <a href="http://bugs.eclipse.org/bugs/">bugzilla
bug reports</a> in time to be considered for the fix pass that
immediately follows, giving rise to the next release candidate.
Throughout the process, we are most concerned with &quot;stop ship&quot;
(P1) bugs that must be fixed before we can declare that we have a
release. If we discover a &quot;stop ship&quot; bug late in the process,
we may have to slip the schedule to allow it to be fixed and retested.
This is why it is so important to ferret out &quot;stop ship&quot; bugs
as early as possible, while there is still time left in the schedule to
address them. Most of the bugs that will be uncovered will be less
serious. During the fix passes, we prioritize the less serious bugs and
try to fix as many of the important ones as possible without
jeopardizing the schedule or the overall stability of the release. We're
always on the look out for &quot;regression&quot; type bugs where we
somehow manage to break something that had been working fine before.
Regressions are an important warning sign that our optimism and
enthusiasm is outpacing our understanding and abilities. Calling special
attention to regressions helps us to collectively bring our head back in
line with our feet, so to speak. With each cycle, we gradually raise the
bar on the kinds and numbers of changes that we will consider making,
until we reach a point where we would only fix &quot;stop ship&quot;
bugs and regressions. (The lesser bugs that we don't end up fixing will
be reconsidered for the next release.) Because of this progressive
tightening, the windows of opportunity for fixing problems within the
schedule are relatively narrow. Things works best if everyone pushes in
the right direction on the right things at the right times. As it is
virtually impossible to work out all the details in advance, we will be
updating this page regularly to reflect current status and current
testing emphasis. If you are participating we suggest you bookmark this
page in your browser and check back frequently for updates. General
announcements during the endgame are posted to the <a href="mailto:platform-releng-dev@eclipse.org">platform-releng-dev@eclipse.org</a>
developer mailing list. Anyone participating in the endgame should be
subscribed to this list, and should direct any general questions and
comments about the process there as well.</p>
</td>
</tr>
</tbody>
</table>
<table cellspacing="5" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td valign="top" align="right" width="2%"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td width="98%"> <p><b><a name="ReleaseCandidate"></a>Release Candidate</b>
- Release candidate builds are like milestone builds. The main difference
is that release candidate builds are usually immediately followed by
a rigorous test pass, whereas milestone builds. We test each release
candidate to find serious bugs and to increase our confidence in what
we have. We then fix the serious bugs in each release candidate to get
the next release candidate, which ought to be even better. Each release
candidate build is kicked off at the indicated time, with the goal being
to have a release candidate available within 24 hours. As the build
is ready, all of the teams validate it and declare it either &quot;go&quot;
of &quot;no go&quot; for testing. Getting a build that is testable may
require a few attempts. These happen in rapid succession, and we continue
rebuilding and revalidating until we have our next release candidate.
It is critical that we have enough time to do test passes. We will slide
the schedule and use weekends as necessary if there are delays of more
than 24 hours in getting a viable release candidate. Note that we will
also do warm-up builds in the days leading up to each release candidate
build to do early integration of fixes.</p>
</td>
</tr>
<tr>
<td valign="top" align="right" width="2%"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td width="98%">
<p><b><a name="TestPass"></a>Test Pass</b> - Once we have a release
candidate build in hand, we enter an intensive test pass for a limited
period of time. Each component team is responsible for preparing a
comprehensive test plan for their component. These component test plans
cover all the functionality that requires manual testing, and identifies
the operating environments in which the testing needs to be done. Each
component team is responsible for staffing and carrying out their test
plan each cycle. Each component team is expected to have most of the
team testing throughout each test pass (a small subset of the team may
be focused on concurrently preparing candidate fixes for &quot;stop
ship&quot; bugs or other high priority tasks). Everyone in the Eclipse
community is encouraged to participate in test passes and report bugs to
<a href="http://dev.eclipse.org/bugs/">bugzilla</a>. Ideally, the bug
report should explicitly call attention to regressions and potential
&quot;stop ship&quot; problems.</p>
</td>
</tr>
<tr>
<td valign="top" align="right" width="2%" height="63"><img src="images/Adarrow.gif" border="0" width="16" height="16"></td>
<td width="98%" height="63">
<p><b><a name="FixPass"></a>Fix Pass</b> - After each test pass, we analyze
and prioritize the set of outstanding bugs and enter an intensive fix
pass for a limited period of time where we try to fix the most pressing
problems. The bugs that we intend to fix for the next release candidate
are tagged accordingly (e.g., a bug tagged as Target 3.2 RC1 should
be fixed as of the release candidate 1 build). &quot;stop ship&quot;
bugs and regressions are always given first priority; less severe problems
are addressed by decreasing priority and as many as possible are fixed
in the time available. With each successive release candidate, we also
tighten the rules for the kinds of changes will be allowed to the code
base and increase the number of people that check the changes before
they are released. The rules apply to any and all changes to the code.
Any committer for any Eclipse component can perform the checking duties.
All committers for a component have the right to veto a change (with
an explanation) even after it has been released into the code base.
If such a veto occurs, the change automatically comes out until the
vetoing committer's concerns are addressed. The committer who releases
a given change, the person that checks the change, and the component
leads that approved making the change in the first place, are jointly
responsible for seeing it through. In other words, we expect a strong
commitment to <em>personally</em> help fix any problems caused by changes
made in fix passes.</p>
</td>
</tr>
</tbody>
</table>
<table cellspacing="5" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td valign="top" align="left" bgcolor="#0080c0" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Details</font></b></td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica"><a name="Transition"></a>Transition
to fix and polish</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Notes:</td>
<td width="75%"> <ul>
<li>All components transition on April 3 to polishing and fixing
bugs for remainder of release cycle.</li>
<li>PMC approval is required for feature work including API changes
being done after April 3.</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC0"></a>RC0/M6</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%"> <ul>
<li>RC0 and milestone M6 are one and the same
<li>All components feature complete.
<li>Accurate prioritization of all outstanding defects.</li>
<li>String externalization complete (including mnemonics).
<li>3.2 test plans posted.</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC1"></a>RC1</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%"> <ul>
<li>Accurate prioritization of all outstanding defects.</li>
<li>All work on polish items complete.</li>
<li>Final API.</li>
<li>No outstanding P1 defects. </li>
<li>As few P2 defects as possible.</li>
</ul>
<p>Note that Fri. April 14 is a holiday in Canada; Mon. April 17
is one in Switzerland.</p></td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="TestPassBeforeRC2"></a>Test
pass prior to RC2</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Notes:</td>
<td width="75%">Full day test pass involving entire community, using
the most recent nightly build to help stabilize HEAD for the upcoming RC2 build.
Committers with high priority fixes to make for RC2 can opt out of testing
to focus on getting in fixes. However, all committers should be working
with the test candidate build.
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC2"></a>RC2</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%">
<ul>
<li>Final artwork in place.
<li>Accurate prioritization of all outstanding defects.
<li>No outstanding P1 defects.
<li>As few P2 defects as possible.</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="TestPassUsingRC2"></a>Test
pass using RC2</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Notes:</td>
<td width="75%">Concerted 2-day testing effort on RC2 involving
entire community including all component teams. In an effort to
mix things up and hold off the onset of &quot;tester
fatigue&quot;, each component team will be designating one team
member that will be assigned to test some other component.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC3"></a>RC3</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%">
<ul>
<li>Accurate prioritization of all outstanding defects.
<li>No outstanding P1 defects.
<li>As few P2 defects as possible.</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="TestPassUsingRC3"></a>Test
pass using RC3</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Notes:</td>
<td width="75%">Concerted 1-day testing effort on RC3 involving
entire community including all component teams, searching for
regressions and on the lookout for undiscovered &quot;stop
ship&quot; defects.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC4"></a>RC4</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%">
<ul>
<li>Accurate prioritization of all outstanding defects.
<li>Stable code base; no outstanding P1 defects. </ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC5"></a>RC5</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%">
<ul>
<li>Documentation work ongoing.
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC6"></a>RC6</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%">
<ul>
<li>Documentation work ongoing.
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="RC7"></a>RC7</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goals:</td>
<td width="75%"> <ul>
<li>Documentation complete.
<li>Accurate prioritization of all outstanding defects.
<li>Stable code base; no outstanding P1 defects</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><font face="Arial,Helvetica" color="#000000"><a name="R3.2"></a>Release
3.2</font></b></td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Goal:</td>
<td width="75%">Ship Eclipse 3.2 during the last week of June.</td>
</tr>
<tr>
<td width="25%">Notes:</td>
<td width="75%">There is no formal test pass for RC4 and beyond other
than to check for last minute regressions. We will perform sanity
checking focused on documentation. Release 3.2 should be complete
and available for download as soon as we are satisfied with it.</td>
</tr>
</table>
</td>
</tr>
</tbody>
</table>
<table cellspacing="5" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td valign="top" align="left" bgcolor="#0080c0" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Fix
pass rules of engagement</font></b></td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b>April 3-14</b><br>
contributions to RC1</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">(1) P1 defects, (2) performance defects, (3) special
&quot;polish&quot; items. Fixing other defects has lower priority.</td>
</tr>
<tr>
<td width="25%">Fix approval:</td>
<td width="75%">Component lead must approve all work on a component.
No changes are to be released without prior approval and
associated bug report tagged 3.2RC1. (Ongoing changes to component
documentation do not require special approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%">Notification requirements:</td>
<td width="75%">None.</td>
</tr>
<tr>
<td width="25%">Extra checking requirements:</td>
<td width="75%">None. (However extra checking is always a good
idea.)</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><a name="FixPassAfterRC1"></a>April
20-28</b><br>
contributions to RC2</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">(1) P1 defects, (2) performance defects, (3) special
&quot;polish&quot; items. Fixing other defects has lower priority.</td>
</tr>
<tr>
<td width="25%" height="48">Fix approval:</td>
<td width="75%" height="48">Component lead must approve all work on
a component. No changes are to be released without prior approval
and associated bug report tagged 3.2RC2. (Ongoing changes to
component documentation do not require special approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%" height="16">Notification requirements:</td>
<td width="75%" height="16">None.</td>
</tr>
<tr>
<td width="25%" height="16">Extra checking requirements:</td>
<td width="75%" height="16">None. (However extra checking is always
a good idea.)</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><a name="FixPassAfterRC2"></a>May
3-5</b><br>
contributions to RC3</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">Serious defects only; documentation.</td>
</tr>
<tr>
<td width="25%">Fix approval:</td>
<td width="75%">Component lead plus one other component lead must
approve all work on a component. No changes are to be released
without prior approval and associated bug report tagged 3.2RC3.
(Ongoing changes to component documentation do not require special
approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%">Notification requirements:</td>
<td width="75%">Announce bug numbers of intended non-doc changes to <a href="mailto:platform-releng-dev@eclipse.org">platform-releng-dev@eclipse.org</a>
mailing list.</td>
</tr>
<tr>
<td width="25%">Extra checking requirements:</td>
<td width="75%">Additional committer must check all code changes
prior to release. Person who reported bug should mark the bug as
verified once they have retested.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><a name="FixPassAfterRC3"></a>May 9-12
</b><br>
contributions to RC4</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">Serious defects only; documentation.</td>
</tr>
<tr>
<td width="25%">Fix approval:</td>
<td width="75%">Component lead plus two other component leads must
approve all non-doc work on a component. In addition, any component
lead can veto a change with cause. No changes are to be released
without associated bug report&nbsp; tagged 3.2RC4 including risk
assessment and prior approvals. (Ongoing changes to component documentation
do not require special approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%">Notification requirements:</td>
<td width="75%">Announce bug numbers of intended non-doc changes to <a href="mailto:platform-releng-dev@eclipse.org">platform-releng-dev@eclipse.org</a>
mailing list.</td>
</tr>
<tr>
<td width="25%">Extra checking requirements:</td>
<td width="75%">Two additional committers must check all code
changes prior to release. Person who reported bug should mark the
bug as verified once they have retested.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><a name="FixPassAfterRC4"></a>May
16-19</b><br>
contributions to RC5</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">Serious defects only; documentation.</td>
</tr>
<tr>
<td width="25%">Fix approval:</td>
<td width="75%">Three committers and a PMC member must approve all
non-doc work on a component. In addition, any committer can
veto a change with cause. No changes are to be released without
associated bug report&nbsp; tagged 3.2RC5 including risk assessment
and prior approvals. (Ongoing changes to component documentation
do not require special approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%">Notification requirements:</td>
<td width="75%">Announce bug numbers of intended non-doc changes to <a href="mailto:platform-releng-dev@eclipse.org">platform-releng-dev@eclipse.org</a>
mailing list.</td>
</tr>
<tr>
<td width="25%">Extra checking requirements:</td>
<td width="75%">Two additional committers must check all code
changes prior to release. Person who reported bug should mark the
bug as verified once they have retested.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><a name="FixPassAfterRC5"></a>May
23-26</b><br>
contributions to RC6</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">Serious defects only; documentation.</td>
</tr>
<tr>
<td width="25%">Fix approval:</td>
<td width="75%">Three committers and a PMC member must approve all
non-doc work on a component. In addition, any committer can
veto a change with cause. No changes are to be released without
associated bug report&nbsp; tagged 3.2RC6 including risk assessment
and prior approvals. (Ongoing changes to component documentation
do not require special approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%">Notification requirements:</td>
<td width="75%">Announce bug numbers of intended non-doc changes to <a href="mailto:platform-releng-dev@eclipse.org">platform-releng-dev@eclipse.org</a>
mailing list.</td>
</tr>
<tr>
<td width="25%">Extra checking requirements:</td>
<td width="75%">Two additional committers must check all code
changes prior to release. Person who reported bug should mark the
bug as verified once they have retested.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="20%" valign="top" align="left"><b><a name="FixPassAfterRC6"></a>May
30-June 2</b><br>
contributions to RC7</td>
<td>
<table cellspacing="0" cellpadding="5" width="100%" border="1">
<tr>
<td width="25%">Focus:</td>
<td width="75%">Serious defects only; documentation.</td>
</tr>
<tr>
<td width="25%">Fix approval:</td>
<td width="75%">Three committers and a PMC member must approve all
non-doc work on a component. In addition, any committer can
veto a change with cause. No changes are to be released without
associated bug report&nbsp; tagged 3.2RC7 including risk assessment
and prior approvals. (Ongoing changes to component documentation
do not require special approval.)</td>
</tr>
<tr>
<td width="25%">API change approval:</td>
<td width="75%">PMC must approve all API changes. No changes are to
be released without prior approval and associated bug report.</td>
</tr>
<tr>
<td width="25%">Notification requirements:</td>
<td width="75%">Announce bug numbers of intended non-doc changes to <a href="mailto:platform-releng-dev@eclipse.org">platform-releng-dev@eclipse.org</a>
mailing list.</td>
</tr>
<tr>
<td width="25%">Extra checking requirements:</td>
<td width="75%">Two additional committers must check all code
changes prior to release. Person who reported bug should mark the
bug as verified once they have retested.</td>
</tr>
</table>
</td>
</tr>
</tbody>
</table>
</body>
</html>