| 84 |
<a name="RELENGMAP"> |
<a name="RELENGMAP"> |
| 85 |
<table border=0 cellspacing=5 cellpadding=2 width="100%"> |
<table border=0 cellspacing=5 cellpadding=2 width="100%"> |
| 86 |
<tr> |
<tr> |
| 87 |
<td align=LEFT valign=TOP bgcolor="#0080C0"> |
<td align=LEFT valign=TOP bgcolor="#0080C0"> <b><font color="#FFFFFF" face="Arial,Helvetica">Making |
| 88 |
<b><font color="#FFFFFF" face="Arial,Helvetica">Making a Build Submission with the Release Engineering Tool</font></b> |
a Build Submission with the Release Engineering Tool</font></b> </td> |
|
</td> |
|
| 89 |
</tr> |
</tr> |
| 90 |
<tr> |
<tr> |
| 91 |
<td> |
<td> <ol> |
| 92 |
<ol> |
<li>Make sure that your workspace contains all of the plug-ins contained |
| 93 |
<li>Make sure that you workspace contains all of the plug-ins |
in our modules. This includes <code>plat-ui</code>, <code>plat-ui-examples</code> |
| 94 |
contained in our modules. This includes <code>plat-ui</code>, |
and <code>plat-ui-tests</code>. Make sure to include fragments that |
| 95 |
<code>plat-ui-examples</code> and <code>plat-ui-tests</code>. Make |
are not appropriate for your platform, as they may need to be versioned |
| 96 |
sure to include fragments that are not appropriate for your |
as well.</li> |
|
platform, as they may need to be versioned as well.</li> |
|
| 97 |
<li>Get rid of all outgoing changes in your workspace.</li> |
<li>Get rid of all outgoing changes in your workspace.</li> |
| 98 |
<li>Run all the test suites. The definitive list of test suites is |
<li>Run all the test suites. The definitive list of test suites is given |
| 99 |
given by inspecting the <code>test.xml</code> files in all our test |
by inspecting the <code>test.xml</code> files in all our test plug-ins. |
| 100 |
plug-ins. At the time of writing, they are roughly: databinding |
At the time of writing, they are roughly: databinding tests, navigator |
| 101 |
tests, navigator tests, parts references tests, session tests, |
tests, parts references tests, session tests, rcp tests, JFace tests, |
| 102 |
rcp tests, JFace tests, and the rather large UiTestSuite. <em>Be |
UI Session tests, and the rather large UiTestSuite. There are launch configurations that you can find in the debug/run launch dialog when you load all the test projects. You can use these to run the tests, rather than creating new ones. <em>Be careful not to disturb focus |
| 103 |
careful not to disturb focus while the test are running. If you're |
while the test are running. If you're leaving the machine running, you |
| 104 |
leaving the machine running, you may wish to increase the time it |
may wish to increase the time it takes for the screensaver to kick in.</em></li> |
| 105 |
takes for the screensaver to kick in.</em></li> |
<li>Run the <a href="cvs-comment.sh">build notes script</a>. On Windows |
| 106 |
<li>Run the <a href="cvs-comment.sh">build notes script</a>. On |
XP, I would recommend installing <a |
| 107 |
Windows XP, I would recommend installing <a |
href="http://www.cygwin.com">cygwin</a>. Check to make sure the list |
| 108 |
href="http://www.cygwin.com">cygwin</a>. Check to make sure the |
of bugs fixed makes sense. To run the build script, execute the following: |
| 109 |
list of bugs fixed makes sense.</li> |
<br> |
| 110 |
<li>Update the <code>buildnotes_workbench.html</code> file with the |
<em> cvs-comment.sh TYYYYMMDD-HHHH HEAD workspace-location > log.txt</em><br> |
| 111 |
results of the build scripts. Commit to CVS.</li> |
where TYYYYMMDD-HHHH is when the build is scheduled to start, HEAD is |
| 112 |
<li>Select a project in the Package Explorer, right-click and select |
the stream to check, workspace location is the directory that contains the build workspace, and log.txt is the file to which the results will |
| 113 |
"Team > Release".</li> |
be written.</li> |
| 114 |
<li>Use the default map project, and then select all the projects in |
<li>Update the <code>org.eclipse.ui/buildnotes_workbench.html</code> file |
| 115 |
the "ui.map" file.</li> |
with the results of the build scripts. Commit to CVS.</li> |
| 116 |
<li>If the release is small, it is a good idea to check the list of |
<li>Select a project in the Package Explorer, right-click and select "Team |
| 117 |
changes.</li> |
> Release".</li> |
| 118 |
<li>Supply the name of the release. Our convention is to use |
<li>Use the default map project, and then select all the projects in the |
| 119 |
TYYYYMMDD-HHHH, where T is the type (e.g., I for an integration |
"ui.map" file.</li> |
| 120 |
build), YYYY is the year, MM is the month, DD is the day and HHHH is |
<li>If the release is small, it is a good idea to check the list of changes.</li> |
| 121 |
the hour the build is scheduled to start. If the name is already in |
<li>Supply the name of the release. Our convention is to use TYYYYMMDD-HHHH, |
| 122 |
use, then use a letter suffix (i.e., a, b, c, etc.).</li> |
where T is the type (e.g., I for an integration build), YYYY is the |
| 123 |
<li>As the commit comment, enter the information from the build |
year, MM is the month, DD is the day and HHHH is the hour the build |
| 124 |
notes script.</li> |
is scheduled to start. If the name is already in use, then use a letter |
| 125 |
|
suffix (i.e., a, b, c, etc.).</li> |
| 126 |
|
<li>As the commit comment, enter the information from the build notes |
| 127 |
|
script.</li> |
| 128 |
<li>Send an email to <a |
<li>Send an email to <a |
| 129 |
href="mailto:platform-ui-dev@eclipse.org">platform-ui-dev</a> with |
href="mailto:platform-ui-dev@eclipse.org">platform-ui-dev</a> with |
| 130 |
the information from the build notes script.</li> |
the information from the build notes script.</li> |
| 131 |
</ol> |
</ol></td> |
| 132 |
</td> |
</tr> |
| 133 |
|
<tr> |
| 134 |
|
<td> </td> |
| 135 |
</tr> |
</tr> |
| 136 |
</table> |
</table> |
| 137 |
<a name="CVSMAP"> |
<a name="CVSMAP"> |
Parent Directory
| 
Revision Log
| 
Patch