diff options
| author | David Williams | 2016-01-23 19:48:04 +0000 |
|---|---|---|
| committer | David Williams | 2016-01-23 19:48:04 +0000 |
| commit | 7a266f7cccd22954d1add7e38383552ba0a01e6c (patch) | |
| tree | 70359e94de86208320e17af1f8575ffd5daaba77 /production/downloadsites | |
| parent | 22d74d1e9aa453a369e1163c5656364b9a177dce (diff) | |
| download | eclipse.platform.releng.aggregator-7a266f7cccd22954d1add7e38383552ba0a01e6c.tar.gz eclipse.platform.releng.aggregator-7a266f7cccd22954d1add7e38383552ba0a01e6c.tar.xz eclipse.platform.releng.aggregator-7a266f7cccd22954d1add7e38383552ba0a01e6c.zip | |
bug 486418 minor fixes and cleanup of Equinox DL site
Diffstat (limited to 'production/downloadsites')
| -rw-r--r-- | production/downloadsites/equinox/build_types.html | 71 |
1 files changed, 0 insertions, 71 deletions
diff --git a/production/downloadsites/equinox/build_types.html b/production/downloadsites/equinox/build_types.html deleted file mode 100644 index 01ff8d0be..000000000 --- a/production/downloadsites/equinox/build_types.html +++ /dev/null @@ -1,71 +0,0 @@ -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> -<html> -<head> -<title>Eclipse Corner</title> -<link rel="stylesheet" href="../default_style.css"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</head> -<body text="#000000" bgcolor="#ffffff" link="#0000ee" vlink="#551a8b" alink="#ff0000"> - <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">Eclipse - Project Build Types</font></b></td> - </tr> - <tr> - <td align=right valign=top><img src="../images/Adarrow.gif" border=0 height=16 width=16></td> - <td> - <p> - <b><font face="arial,helvetica,geneva" size="-1">Releases</font></b> <br> <font size="-1" - face="arial,helvetica,geneva"> </font>Releases are builds that have been declared major releases by the development team - - for example "R1.0". Releases are the right builds for people who want to be on a stable, tested release, and - don't need the latest greatest features and improvements. Release builds always have an "R" at the beginning of - the name i.e. R1.0, R2.0 etc. Non-release <font size="-1" face="arial,helvetica,geneva"> builds are named according - to the date of the build - for example 20011027 is the build from Oct 27, 2001.</font><br> - </p> - </td> - </tr> - <tr> - <td align=right valign=top><img src="../images/Adarrow.gif" border=0 height=16 width=16></td> - <td><b><font face="arial,helvetica,geneva" size="-1">Stable Builds</font></b> <br> <font size="-1" - face="arial,helvetica,geneva"> Stable builds are integration builds that have been found to be stable enough for most - people to use. They are promoted from integration build to stable build by the architecture team after they have been used - for a few days and deemed reasonably stable. The latest stable build is the right build for people who want to stay up to - date with what is going on in the latest development stream, and don't mind putting up with a few problems n in order to - get the latest greatest features and bug fixes. The latest stable build is the one the development team likes people to be - using, because of the valuable and timely feedback. </font></td> - </tr> - <tr> - <td align=right valign=top><img src="../images/Adarrow.gif" border=0 height=16 width=16></td> - <td> - <p> - <b><font face="arial,helvetica,geneva" size="-1">Integration Builds</font></b> <br> <font size="-1" - face="arial,helvetica,geneva"> Periodically, component teams version off their work in what they believe is a - stable, consistent state, and they update the build configuration to indicate that the next integration build should - take this version of the component. Integration builds are built from these stable component versions that have been - specified by each component team as the best version available. Integration builds may be promoted to stable builds - after a few days of testing. Integration builds are built whenever new stable component versions are released into the - build.</font> - </p> - </td> - </tr> - <TR> - <TD ALIGN=right VALIGN=top><IMG SRC="../images/Adarrow.gif" BORDER=0 HEIGHT=16 WIDTH=16></TD> - <TD><B><FONT FACE="arial,helvetica,geneva" SIZE="-1">Nightly Builds</FONT></B><BR> <FONT SIZE="-1" - FACE="arial,helvetica,geneva"> Nightly builds are produced every night from whatever has been released into the - master branch of the Git repository. They are completely untested and will almost always have major problems. Many will - not work at all. These drops are normally only useful to developers actually working on the Eclipse Project. Because - nightly builds are produced in a different way from integration builds, bundles from nightly builds should not be mixed - with bundles from other types of builds. </FONT></TD> - </TR> - <TR> - <TD ALIGN=right VALIGN=top><IMG SRC="../images/Adarrow.gif" BORDER=0 HEIGHT=16 WIDTH=16></TD> - <TD><B><FONT FACE="arial,helvetica,geneva" SIZE="-1">Maintenance Builds</FONT></B><BR> <FONT SIZE="-1" - FACE="arial,helvetica,geneva"> Maintenance builds are produced periodically to incorporate fixes into an existing - release. They are typically built from tagged plug-in and feature pojects in a maintenance branch of the Git repository - (i.e. R3_7_maintenance). Maintenance builds are promoted to a minor or service release (i.e. R3.7 or R3.7.1) after - development teams have deemed one to be stable following one or more test-fix pass cycles. </FONT></TD> - </TR> - </table> - <h3> </h3> -</body> -</html> |