platform-ui-home/builds/index.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2, Mon Oct 20 21:27:28 2003 UTC revision 1.3, Tue Oct 21 18:59:18 2003 UTC
# Line 9  Line 9 
9    
10  <table border=0 cellspacing=5 cellpadding=2 width="100%" >  <table border=0 cellspacing=5 cellpadding=2 width="100%" >
11    <tr>    <tr>
12      <td align=LEFT valign=TOP colspan="2" bgcolor="#0080C0"><b><font color="#FFFFFF" face="Arial,Helvetica">      <td align=left width="72%">
13        Builds (Platform-UI)</font></b></td>        <font class=indextop>Builds</font><br>
14          <font class=indexsub>platform user interface</font>
15        </td>
16        <td width="28%">
17          <img src="http://dev.eclipse.org/images/Idea.jpg" height=86 width=120 alt="Eclipse documentation banner">
18        </td>
19      </tr>
20    </table>
21    <table border=0 cellspacing=5 cellpadding=2 width="100%">
22      <tr>
23        <td align=LEFT valign=TOP bgcolor="#0080C0">
24          <b><font color="#FFFFFF" face="Arial,Helvetica">Topics</font></b>
25        </td>
26      </tr>
27      <tr>
28        <td width="98%">
29          <b>Topics</b>
30          <ul>
31            <li><a href="#BUILDS">Build Submissions</a></li>
32            <li><a href="#INSTALLING">Installing Release Engineering Tools</a></li>
33            <li><a href="#RELENGMAP">Making a Build Submission with Release
34            Engineering Tools</a></li>
35            <li><a href="#CVSMAP">Making a Build Submission with CVS Only</a></li>
36            <li><a href="#RECOVERY">Recovery Builds</a></li>
37          </ul>
38        </td>
39    </tr>    </tr>
40    </table>
41    <a name="BUILDS">
42    <table border=0 cellspacing=5 cellpadding=2 width="100%">
43    <tr>    <tr>
44      <td align=right valign=top width="2%"><img src="http://dev.eclipse.org/images/Adarrow.gif" border=0 height=16 width=16      <td align=LEFT valign=TOP bgcolor="#0080C0">
45          alt = "Eclipse idea banner"></td>        <b><font color="#FFFFFF" face="Arial,Helvetica">Build Submissions</font></b>
46      <td width="98%"><p>Build submissions are done before every integration build      </td>
47          and milestone build.  Integration builds typically occur on Tuesday.    </tr>
48          So, the official build submission tends to occur every Monday at 4 p.m.    <tr>
49          (Eastern Time).  This is moved to Tuesday if Monday was a Canadian      <td width="98%">
50          holiday.  If you miss the cut-off for the official build submission, but          <p>Build submissions are done before every integration build and
51          it is still before 8 a.m. on Tuesday, then you can do your own build          milestone build.  Integration builds typically occur on Tuesday.  Please
52          submission to make sure your fix gets into the integration build.  A          see the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/index.html">Platform
53          warning email should be sent to "platform-ui-dev@eclipse.org" at          Release Engineering</a> page for more information.  We do our build
54          the beginning of the days on which an official build submission is to          submission for an 8 a.m. build, at 4 p.m. the previous day.</p>
55          occur, and if you do your own build submission.</p>          <p>If you miss the cut-off for the official build submission, but
56            it is still before the build has started, then you can do your own build
57            submission to make sure your fix gets into the build.</p>
58            <p>A warning email should be sent to "platform-ui-dev@eclipse.org" (or
59            all committers) at the beginning of the days on which an official build
60            submission is to occur, or if you do your own build submission.</p>
61      </tr>
62    </table>
63    <a name="INSTALLING">
64    <table border=0 cellspacing=5 cellpadding=2 width="100%">
65      <tr>
66        <td align=LEFT valign=TOP bgcolor="#0080C0">
67          <b><font color="#FFFFFF" face="Arial,Helvetica">Installing the Release Engineering Tool</font></b>
68        </td>
69      </tr>
70      <tr>
71            <td>
72          <p>The Platform-UI team suggests that the Release Engineering (releng)          <p>The Platform-UI team suggests that the Release Engineering (releng)
73          tool be installed before doing a build submission.  It reduces the          tool be installed before doing a build submission.  It reduces the
74          chance of error.</p>          chance of error.</p>
# Line 34  Line 78 
78          <li>Unzip the tool into your <code>plugins</code> directory.</li>          <li>Unzip the tool into your <code>plugins</code> directory.</li>
79          <li>Start Eclipse</li>          <li>Start Eclipse</li>
80        </ol>        </ol>
81        </td>
82      </tr>
83    </table>
84    <a name="RELENGMAP">
85    <table border=0 cellspacing=5 cellpadding=2 width="100%">
86      <tr>
87        <td align=LEFT valign=TOP bgcolor="#0080C0">
88          <b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with the Release Engineering Tool</font></b>
89        </td>
90      </tr>
91      <tr>
92        <td>
93          <p>Before performing an build submission, it is the responsibility of          <p>Before performing an build submission, it is the responsibility of
94          the submitter to verify that the UI tests all pass.  To perform a          the submitter to verify that the UI tests all pass.  To perform a
95          submission using the releng tool, please do as follows:</p>          submission using the releng tool, please do as follows:</p>
# Line 48  Line 104 
104          <li>Continue to version all of the packages that you need.</li>          <li>Continue to version all of the packages that you need.</li>
105          <li>When you are done, commit the changes to "<code>ui.map</code>".          <li>When you are done, commit the changes to "<code>ui.map</code>".
106        </ol>        </ol>
107        </td>
108      </tr>
109    </table>
110    <a name="CVSMAP">
111    <table border=0 cellspacing=5 cellpadding=2 width="100%">
112      <tr>
113        <td align=LEFT valign=TOP bgcolor="#0080C0">
114          <b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with CVS Only</font></b>
115        </td>
116      </tr>
117      <tr>
118            <td>
119          <p>To do a build submission using CVS, please do as follows:</p>          <p>To do a build submission using CVS, please do as follows:</p>
120        <ol>        <ol>
121          <li>Tag all projects you have changed with the name of the release.  Our          <li>Tag all projects you have changed with the name of the release.  Our
# Line 60  Line 128 
128          <li>Save the map.</li>          <li>Save the map.</li>
129          <li>Commit your changes to the map to CVS.</li>          <li>Commit your changes to the map to CVS.</li>
130        </ol>        </ol>
131          <p>
132      </td>      </td>
133    </tr>    </tr>
134  </table>  </table>
135    <a name="RECOVERY">
136    <table border=0 cellspacing=5 cellpadding=2 width="100%">
137      <tr>
138        <td align=LEFT valign=TOP bgcolor="#0080C0">
139          <b><font color="#FFFFFF" face="Arial,Helvetica">Recovery Builds</font></b>
140        </td>
141      </tr>
142            <td>
143              <p>In the event of a test failure, our team must respond to
144              <a href="mailto:eclipse-dev@eclipse.org">eclipse-dev</a> with one of two
145              responses.  We can say that we want a recovery build the following day.
146              Alternatively, we can say that the test failure is not significant, and
147              that the quality of the build should not be affected.  (In either case, a
148              bug should likely be entered into the bug database.)</p>
149              <p>A recovery build can also be requested if there is a problem affecting
150              the usability of the build.  This problem should make the build unusable
151              for testing and development use.</p>
152              <p>For a recovery build, the map will need to be updated to include our
153              fixes.  This can either be everything on the head in CVS, or just the
154              particular fixes we need.  The former should only be done if no risky
155              changes have gone onto the head since the last (i.e., the failed) build
156              submission.</p>
157            </td>
158      <tr>
159      </tr>
160    </table>
161  </body>  </body>
162  </html>  </html>
Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3