platform-ui-home/builds/index.html

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

revision 1.7, Fri Apr 16 15:49:10 2004 UTC revision 1.8, Tue Jun 15 13:39:34 2004 UTC
# Line 28  Line 28 
28      <td width="98%">      <td width="98%">
29        <b>Topics</b>        <b>Topics</b>
30        <ul>        <ul>
31            <li><a href="#FIXES">Upcoming Fixes</a></li>
32          <li><a href="#BUILDS">Build Submissions</a></li>          <li><a href="#BUILDS">Build Submissions</a></li>
33          <li><a href="#INSTALLING">Installing Release Engineering Tools</a></li>          <li><a href="#INSTALLING">Installing Release Engineering Tools</a></li>
34          <li><a href="#RELENGMAP">Making a Build Submission with Release          <li><a href="#RELENGMAP">Making a Build Submission with Release
# Line 38  Line 39 
39      </td>      </td>
40    </tr>    </tr>
41  </table>  </table>
42    <a name="FIXES">
43    <table border=0 cellspacing=5 cellpadding=2 width="100%">
44      <tr>
45        <td align=LEFT valign=TOP bgcolor="#0080C0">
46          <b><font color="#FFFFFF" face="Arial,Helvetica">Upcoming Fixes</font></b>
47        </td>
48      </tr>
49      <tr>
50        <td width="98%">
51            <p>If you're lucky, then there is a <a href="fixedBugs.html">list of
52            fixes</a> that are expected to appear in the next integration
53            build.</p>
54        </td>
55      </tr>
56    </table>
57  <a name="BUILDS">  <a name="BUILDS">
58  <table border=0 cellspacing=5 cellpadding=2 width="100%">  <table border=0 cellspacing=5 cellpadding=2 width="100%">
59    <tr>    <tr>
# Line 96  Line 112 
112        <ol>        <ol>
113          <li>Select the project you need to version, and select "Team >          <li>Select the project you need to version, and select "Team >
114          Release".</li>          Release".</li>
115          <li>Supply the name of the release.  Our convention is to use vYYYYMMDD,          <li>Supply the name of the release.  Our convention is to use
116          where the date is the day of the build.  If the name is already in use,          vYYYYMMDDHHHH, where this the date and the time of the build.  If the
117          then use a letter suffix (i.e., a, b, c, etc.).</li>          name is already in use, then use a letter suffix (i.e., a, b, c,
118            etc.).</li>
119          <li>The synchronize view will open showing the changes in the file          <li>The synchronize view will open showing the changes in the file
120          "<code>ui.map</code>".</li>          "<code>ui.map</code>".</li>
121          <li>Continue to version all of the packages that you need.</li>          <li>Continue to version all of the packages that you need.</li>
# Line 119  Line 136 
136        <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>
137        <ol>        <ol>
138          <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
139          convention is to use vYYYYMMDD, where the date is the day of the build.          convention is to use vYYYYMMDDHHHH, where this the date and time of the
140          If the name is already in use, then use a letter suffix (i.e., a, b, c,          build.  If the name is already in use, then use a letter suffix (i.e.,
141          etc.).</li>          a, b, c, etc.).</li>
142          <li>Checkout "org.eclipse.releng".</li>          <li>Checkout "org.eclipse.releng".</li>
143          <li>Open "<code>maps/ui.map</code>".</li>          <li>Open "<code>maps/ui.map</code>".</li>
144          <li>Change the version(s) of the project(s) you have tagged.</li>          <li>Change the version(s) of the project(s) you have tagged.</li>
Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8