platform-ui-home/builds/index.html
Parent Directory
| 
Revision Log
Revision 1.8 -
(download)
(as text)
(annotate)
Tue Jun 15 13:39:34 2004 UTC (5 years, 5 months ago) by dpollock
Branch: MAIN
Changes since 1.7: +23 -6 lines
Tue Jun 15 13:39:34 2004 UTC (5 years, 5 months ago) by dpollock
Branch: MAIN
Changes since 1.7: +23 -6 lines
+ Added some information about the list of fixed bugs. + Changed the tagging format to include the time.
<html> <head> <title>Builds (Platform-UI)</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css"> </head> <body bgcolor="#FFFFFF" text="#000000"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=left width="72%"> <font class=indextop>Builds</font><br> <font class=indexsub>platform user interface</font> </td> <td width="28%"> <img src="http://dev.eclipse.org/images/Idea.jpg" height=86 width=120 alt="Eclipse documentation banner"> </td> </tr> </table> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Topics</font></b> </td> </tr> <tr> <td width="98%"> <b>Topics</b> <ul> <li><a href="#FIXES">Upcoming Fixes</a></li> <li><a href="#BUILDS">Build Submissions</a></li> <li><a href="#INSTALLING">Installing Release Engineering Tools</a></li> <li><a href="#RELENGMAP">Making a Build Submission with Release Engineering Tools</a></li> <li><a href="#CVSMAP">Making a Build Submission with CVS Only</a></li> <li><a href="#RECOVERY">Recovery Builds</a></li> </ul> </td> </tr> </table> <a name="FIXES"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Upcoming Fixes</font></b> </td> </tr> <tr> <td width="98%"> <p>If you're lucky, then there is a <a href="fixedBugs.html">list of fixes</a> that are expected to appear in the next integration build.</p> </td> </tr> </table> <a name="BUILDS"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Build Submissions</font></b> </td> </tr> <tr> <td width="98%"> <p>Build submissions are done before every integration build and milestone build. Integration builds typically occur on Tuesday. Please see the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/index.html">Platform Release Engineering</a> page for more information. We do our build submission for an 8 a.m. build, at 4 p.m. the previous day.</p> <p>If you miss the cut-off for the official build submission, but it is still before the build has started, then you can do your own build submission to make sure your fix gets into the build.</p> <p>A warning email should be sent to "platform-ui-dev@eclipse.org" (or all committers) at the beginning of the days on which an official build submission is to occur, or if you do your own build submission.</p> </tr> </table> <a name="INSTALLING"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Installing the Release Engineering Tool</font></b> </td> </tr> <tr> <td> <p>The Platform-UI team suggests that the Release Engineering (releng) tool be installed before doing a build submission. It reduces the chance of error.</p> <ol> <li>Exit Eclipse (if running)</li> <li>Download the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/org.eclipse.releng.tools_3.0.4.zip">releng tool</a>.</li> <li>Unzip the tool into your <code>plugins</code> directory.</li> <li>Start Eclipse</li> </ol> </td> </tr> </table> <a name="RELENGMAP"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with the Release Engineering Tool</font></b> </td> </tr> <tr> <td> <p>Before performing an build submission, it is the responsibility of the submitter to verify that the UI tests all pass. To perform a submission using the releng tool, please do as follows:</p> <ol> <li>Select the project you need to version, and select "Team > Release".</li> <li>Supply the name of the release. Our convention is to use vYYYYMMDDHHHH, where this the date and the time of the build. If the name is already in use, then use a letter suffix (i.e., a, b, c, etc.).</li> <li>The synchronize view will open showing the changes in the file "<code>ui.map</code>".</li> <li>Continue to version all of the packages that you need.</li> <li>When you are done, commit the changes to "<code>ui.map</code>". </ol> </td> </tr> </table> <a name="CVSMAP"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with CVS Only</font></b> </td> </tr> <tr> <td> <p>To do a build submission using CVS, please do as follows:</p> <ol> <li>Tag all projects you have changed with the name of the release. Our convention is to use vYYYYMMDDHHHH, where this the date and time of the build. If the name is already in use, then use a letter suffix (i.e., a, b, c, etc.).</li> <li>Checkout "org.eclipse.releng".</li> <li>Open "<code>maps/ui.map</code>".</li> <li>Change the version(s) of the project(s) you have tagged.</li> <li>Save the map.</li> <li>Commit your changes to the map to CVS.</li> </ol> <p> </td> </tr> </table> <a name="RECOVERY"> <table border=0 cellspacing=5 cellpadding=2 width="100%"> <tr> <td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Recovery Builds</font></b> </td> </tr> <td> <p>In the event of a test failure, our team must respond to <a href="mailto:eclipse-dev@eclipse.org">eclipse-dev</a> with one of two responses. We can say that we want a recovery build the following day. Alternatively, we can say that the test failure is not significant, and that the quality of the build should not be affected. (In either case, a bug should likely be entered into the bug database.)</p> <p>A recovery build can also be requested if there is a problem affecting the usability of the build. This problem should make the build unusable for testing and development use.</p> <p>For a recovery build, the map will need to be updated to include our fixes. This can either be everything on the head in CVS, or just the particular fixes we need. The former should only be done if no risky changes have gone onto the head since the last (i.e., the failed) build submission.</p> </td> <tr> </tr> </table> </body> </html>
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |