blob: f3f0ce30ccf5b6a00f7d8d39040112a4b66643c9 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# index.php
#
# Author:
# Date: 2015-11-26
#
# Description: Eclipse project 4.5.2 release freeze plan
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "Eclipse Mars.2 (4.5.2) Endgame Plan";
$pageKeywords = "eclipse, 4.5.2, SR2, milestone, schedule, endgame";
$pageAuthor = "";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the markers!
ob_start();
?>
<style type="text/css">
table.schedule td {font-weight:bold; padding-left:10px;}
table.schedule td.date {font-weight:normal; }
table.schedule td.spacer {padding-top:10px; padding-bottom:10px; }
table.schedule tr.current td {
background-color: #F4EEFF;
}
</style>
<div id="midcolumn">
<h1><?= $pageTitle ?></h1>
<div class="homeitem3col">
<h3>Status</h3>
<p><b>Weekly maintenance builds until December 31</b></p>
</div>
<div class="homeitem3col">
<h3>Detailed Timeline</h3>
<table class="schedule" border="0" cellspacing="0" align="center" width=100%>
<tr class="current">
<td>Until December 31, 2015</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Weekly maintenance builds</td>
<td></td>
</tr>
<tr>
<td class="spacer">&nbsp;</td>
</tr>
<tr>
<td>January 2016</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Weekly maintenance builds</td>
<td></td>
</tr>
<tr>
<td class="spacer">&nbsp;</td>
</tr>
<tr>
<td></td>
<td class="date">13</td>
<td class="date">Wed 08:00 EDT</td>
<td></td>
<td>Release Candidate 1 build</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">15</td>
<td class="date">Fri</td>
<td></td>
<td>Submit to release train</td>
<td></td>
</tr>
<tr>
<td class="spacer">&nbsp;</td>
</tr>
<tr>
<td></td>
<td class="date">27</td>
<td class="date">Wed 08:00 EDT</td>
<td></td>
<td>Release Candidate 2 build</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">28</td>
<td class="date">Thu 08:00 EDT</td>
<td></td>
<td>1-day test pass against RC2 and sign-off</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">29</td>
<td class="date">Fri</td>
<td></td>
<td>Submit to release train</td>
<td></td>
</tr>
<tr>
<td>February 2016</td>
</tr>
<tr>
<td class="spacer">&nbsp;</td>
</tr>
<tr>
<td></td>
<td class="date">3</td>
<td class="date">Wed 08:00 EDT</td>
<td></td>
<td>Release Candidate 3 build</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">4</td>
<td class="date">Thu 08:00 EDT</td>
<td></td>
<td>1-day test pass against RC3 and sign-off</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">5</td>
<td class="date">Fri</td>
<td></td>
<td>Submit to release train</td>
<td></td>
</tr>
<tr>
<td class="spacer">&nbsp;</td>
</tr>
<tr>
<td></td>
<td class="date">10</td>
<td class="date">Wed 08:00 EDT</td>
<td></td>
<td>Release Candidate 4 build [if required]</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">12</td>
<td class="date">Fri</td>
<td></td>
<td>Submit to release train [if required]</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">19</td>
<td class="date">Fri</td>
<td></td>
<td>Simultaneous release train complete with RC4</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">20 to 25</td>
<td class="date"></td>
<td></td>
<td>Quiet week/buffer</td>
<td></td>
</tr>
<tr>
<td></td>
<td class="date">26</td>
<td class="date">Fri</td>
<td></td>
<td>Simultaneous release train GA Mars.2</td>
<td></td>
</tr>
</table>
<p>
Here are some holidays and other dates during the freeze period to keep in mind:
<ul>
<li>January 29 - Mars M5</li>
<li>February 15 - Canada</li>
</ul>
</p>
</div>
<div class="homeitem3col">
<h3>Useful Links</h3>
<ul>
<li><a href="http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html">Build Schedule</a> - details on build times.</li>
<li><a href="http://wiki.eclipse.org/Eclipse/Release_checklist">Eclipse Release Checklist</a> - lists various things that need to be checked before each release.</li>
<li><a href="http://www.eclipse.org/projects/project-plan.php?projectid=eclipse">Eclipse Project Mars Plan</a></li>
<li><a href="http://wiki.eclipse.org/index.php/Mars">Mars Simultaneous Release</a></li>
</ul>
</div>
<div class="homeitem3col">
<h3>What is the game plan?</h3>
<p>
The Eclipse Mars Service Release 2 ("Mars.2 (4.5.2)") endgame involves building
a series of release candidates leading to the Eclipse project's contribution to the
Mars.2 (4.5.2) release. The Eclipse project version number for this release is 4.5.2.
By its nature, this maintenance release contains fixes to a small number
of serious problems found in the June 2015 Mars (4.5) release. We make and verify each
fix carefully, so that we do not need to tie up the entire development
team in time-consuming test passes. As always, we welcome help from the
community with testing the release candidates. By default, Mars.2 (4.5.2)
is supposed to work exactly like the initial Mars (4.5) release except for the problems we intended
to fix. All problems fixed in Mars.2 (4.5.2) are in the Eclipse bugzilla database
and flagged with Target Milestone &quot;4.5.2&quot; (query bugzilla for
the <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;resolution=FIXED;target_milestone=4.5.2&target_milestone=Mars%20SR2;product=Equinox;product=JDT;product=PDE;product=Platform;classification=Eclipse;classification=RT">complete
list of bugs fixed in Mars.2 (4.5.2)</a>). So we're most interested in identifying
regressions where we've changed something that we did not intend to.
</p>
<p>General announcements during the Mars.2 (4.5.2) endgame are posted to the
<a href="http://dev.eclipse.org/mailman/listinfo/platform-releng-dev">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>
<strong>RC1</strong>
<p>
Release candidate 1 is a warm-up build to ensure the release train build
process is in place and all projects are making contributions. All fixes submitted
to maintenance stream builds must have a component lead or PMC vote on the bug report,
and the fix must be reviewed by an additional committer (any committer other than
the one who made the fix).
</p>
<strong>RC2</strong>
<p>
Release candidate containing fixes for the majority of known outstanding
defects that we intend to fix for Mars.2 (4.5.2). At the end of RC2 build,
there should not be any open defects tagged 4.5.2. All fixes submitted
to maintenance stream builds must have a component lead or PMC vote on the bug report,
and the fix must be reviewed by an additional committer (any committer other than
the one who made the fix).
</p>
<strong>Test pass using RC2</strong>
<p>Concerted 1-day testing effort using RC2 involving entire community including
all component teams. The goal is to verify all the fixes and check for any regressions.
</p>
<strong>RC3</strong>
<p>Release candidate containing fixes for all known outstanding defects
that we intend to fix for Mars.2 (4.5.2). All fixes submitted to RC3 must have a PMC vote on the bug report,
and the fix must be reviewed by an additional committer (any committer other than
the one who made the fix).
Ensure that all feature/plugin versions have been consistently incremented when needed.
</p>
<strong>Test pass using RC3</strong>
<p>Concerted 1-day testing effort using RC3 involving entire community
including all component teams. The goal is to verify all the fixes, check
for any regressions and sanity check our RC3 candidate.
</p>
<strong>RC4</strong>
<p>Release candidate 4, if required, to fix problems detected during the test pass.
We expect NO CHANGE at this point. If you find a show stopper, please notify ASAP the
<a href="http://dev.eclipse.org/mailman/listinfo/eclipse-pmc">eclipse-pmc@eclipse.org</a> mailing list.
All fixes submitted to RC4 must have a PMC vote on the bug report and be reviewed
by an additional committer (any committer other than the one who made the fix).
</p>
<p>No test pass is scheduled unless significant contributions occurred. If so,
then Thursday would be elected for a one day test pass</p>
<strong>API change approval</strong>
<p>
No API changes are expected during a maintenance release. Any exception must be
approved by the PMC. No changes are to be released without prior approval
and associated bug report. Send the request for approval to the eclipse-pmc
mailing list. If a change is made to API to make it binary compatible with
a previous release, technically this is still an API change, and thus it should be treated
in the same way as any other API change requests.
</p>
<strong>Mars.2 (4.5.2) Release</strong>
<p>The Mars.2 (4.5.2) release should be complete and available for download by
the end of February 2016 as part of the <a href="http://wiki.eclipse.org/Mars">Mars
coordinated service release</a> . If product teams intending
to ship on Mars.2 (4.5.2) uncover further serious defects during the endgame,
we may schedule additional release candidate builds to incorporate fixes.
</p>
</div>
</div>
<?php
$html = ob_get_contents();
ob_end_clean();
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>