Home | History | Annotate | Download | only in dropSiteRootFiles
      1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
      2 <html>
      3 <head>
      4 <title>Eclipse Corner</title>
      5 <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css">
      6 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
      7 </head>
      8 <body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000">
      9 <table border=0 cellspacing=5 cellpadding=2 width="100%" > <tr> <td align=left valign=top colspan="2" bgcolor="#0080c0"><b><FONT FACE="Arial,Helvetica" COLOR="#ffffff">&lt;your 
     10 project&gt; Build Types</FONT></b></td></tr> <tr> <td align=right valign=top><img src="http://dev.eclipse.org/images/Adarrow.gif" border=0 height=16 width=16></td><td> 
     11 <p><b><font face="arial,helvetica,geneva" size="-1">Releases</font></b> <br> <font size="-1" face="arial,helvetica,geneva"> 
     12 </font>Releases are builds that have been declared major releases by the development 
     13 team - for example &quot;R1.0&quot;. Releases are the right builds for people 
     14 who want to be on a stable, tested release, and don't need the latest greatest 
     15 features and improvements. <font size="-1" face="arial,helvetica,geneva"> Release 
     16 builds always have an &quot;R&quot; at the beginning of the name i.e. R1.0, R2.0 
     17 etc. Non-release builds are named according to the date of the build - for example 
     18 20011027 is the build from Oct 27, 2001.</font><br> </p></td></tr> <tr> <td align=right valign=top><img src="http://dev.eclipse.org/images/Adarrow.gif" border=0 height=16 width=16></td><td><b><font face="arial,helvetica,geneva" size="-1">Stable 
     19 Builds</font></b> <br> <font size="-1" face="arial,helvetica,geneva"> Stable builds 
     20 are integration builds that have been found to be stable enough for most people 
     21 to use. They are promoted from integration build to stable build by the architecture 
     22 team after they have been used for a few days and deemed reasonably stable. The 
     23 latest stable build is the right build for people who want to stay up to date 
     24 with what is going on in the latest development stream, and don't mind putting 
     25 up with a few problems in order to get the latest greatest features and bug fixes. 
     26 The latest stable build is the one the development team likes people to be using, 
     27 because of the valuable and timely feedback. </font></td></tr> <tr> <td align=right valign=top><img src="http://dev.eclipse.org/images/Adarrow.gif" border=0 height=16 width=16></td><td> 
     28 <p><b><font face="arial,helvetica,geneva" size="-1">Integration Builds</font></b> 
     29 <br> <font size="-1" face="arial,helvetica,geneva"> Periodically, component teams 
     30 version off their work in what they believe is a stable, consistent state, and 
     31 they update the build configuration to indicate that the next integration build 
     32 should take this version of the component. Integration builds are built from these 
     33 stable component versions that have been specified by each component team as the 
     34 best version available. Integration builds may be promoted to stable builds after 
     35 a few days of testing. Integration builds are built whenever new stable component 
     36 versions are released into the build.</font></p></td></tr> <tr> <td align=right valign=top><img src="http://dev.eclipse.org/images/Adarrow.gif" border=0 height=16 width=16></td><td><b><font face="arial,helvetica,geneva" size="-1">Nightly 
     37 Builds</font></b><br> <font size="-1" face="arial,helvetica,geneva"> Nightly builds 
     38 are produced over night from whatever has been released into the HEAD stream of 
     39 the CVS repository. They are completely untested and will almost always have major 
     40 problems. Many will not work at all. These drops are normally only useful to developers 
     41 actually working on the &lt;your project&gt;.<BR> <BR>Note: Nightly builds are 
     42 produced only as requested, and not necessarily every night, by developers to 
     43 build what was in HEAD. </font></td></tr> <tr> <td align=right valign=top><img src="http://dev.eclipse.org/images/Adarrow.gif" border=0 height=16 width=16></td><td> 
     44 <p><b><font face="arial,helvetica,geneva" size="-1">Maintenance Builds</font></b> 
     45 <br> <font size="-1" face="arial,helvetica,geneva">Periodically builds for maintenance 
     46 of the current release will be performed. They will not necessarily be stable 
     47 builds. When the maintenace is finalized and released, it will be moved up to 
     48 a Release build. If the build name starts with an &quot;M&quot; i.e. M20031110, 
     49 then it has not been tested for stability. If it is a release candidate, i.e. 
     50 0.5.0.1RC1, then it is a stable maintenance build.</font></p></td></tr> </table><h3>&nbsp;</h3>
     51 </body>
     52 </html>
     53