|
|
| Line 1: |
Line 1: |
| − | Many non-platform build teams rely of the plugins in org.eclipse.releng.basebuilder to run their builds. This page will serve to notify build teams of recent changes to basebuilder so they may incorporate changes as appropriate.
| + | == General == |
| | | | |
| − | By using the HEAD version of org.eclipse.releng.basebuilder, there may be unexpected changes at times. Building from HEAD is advised for people who like to live on the edge :-). A version of org.eclipse.releng.basebuilder is tagged after every milestone before we upgrade to the lastest milestone plugins. For instance, version M2_32 of org.eclipse.releng.basebuilder reflects the version of org.eclipse.releng.basebuilder that was used to build 3.2 M2 and may provide additional stability than HEAD.
| + | * Is it fun writing code for the CDT? |
| | | | |
| − | <h5>May 2, 2006</h5>
| + | You betcha! And the Eclipse SDK is such a great environment to work in. We've pumped out quality code by the boat load without a lot of effort. |
| − | 3.2RC2 plugins have been moved to releng_test and tagged with RC2_32. Also, there is a new version of jdt.core because we are testing it at the same time. In plugins/org.eclipse.build.tools, there is the code from Bug 116912 Release Train Cascade / RSS Notification & Response that the EMF team contributed. However, I haven't modified our builder to use this code yet.
| + | |
| | | | |
| − | <h5>April 18, 2006</h5>
| + | == Release Engineering == |
| − | 3.2RC1 plugins have been moved to HEAD and tagged with RC1_32. I didn't have to make any changes to the builder to accommodate the new plugins.
| + | |
| | | | |
| − | <h5>April 6, 2006</h5>
| + | * Where can I get the latest builds? |
| − | We have tagged HEAD with M6_32 because the M6 plugins have been moved to HEAD + a new org.eclipse.help.base for the following
| + | |
| − | https://bugs.eclipse.org/bugs/show_bug.cgi?id=134857
| + | |
| | | | |
| − | <h5>February 22, 2006</h5>
| + | We have a build machine, [http://cdt.eclipse.org cdt.eclipse.org], that we use for our builds. You can access them from the builds section on its home page. You can also generate your own builds by checking out the CDT out of CVS and using the Export -> Deployable Feature menu item provided by the PDE. |
| − | We have tagged HEAD with M5_32 because the M5 plugins have been moved to HEAD. | + | |
| − | | + | |
| − | <h5>February 20, 2006</h5>
| + | |
| − | We have tagged HEAD with M4_32. We actually used version I20060217-1115 to build Eclipse M5 which had a newer version of PDE build than was provided by M4 + a help fix.
| + | |
| − | | + | |
| − | <h5>December 19, 2005</h5>
| + | |
| − | We are holding off moving to new plugins in HEAD until the New Year. When we do release the new plugins to HEAD, they will be M4 + a fix from Help. https://bugs.eclipse.org/bugs/show_bug.cgi?id=121098
| + | |
| − | | + | |
| − | <h5>November 9, 2005</h5>
| + | |
| − | For build teams that use org.eclipse.basebuilder project in their builds, tag M3_32 of org.eclipse.releng.basebuilder is now available. This tag refers to a version of basebuilder that consists of plugins from Eclipse 3.2 M3. We would strongly advise all teams not to use the HEAD version of org.eclipse.releng.basebuilder in their builds as this is a development stream. We would advise all teams to either use the stable tags M2_32 (plugins from milestone 2) or M3_32 (plugins from milestone 3) of org.eclipse.releng.basebuilder.
| + | |
| − | | + | |
| − | <h5>November 7, 2005 changes</h5>
| + | |
| − | HEAD stream of org.eclipse.releng.basebuilder tagged as version M2_32. Subsequently, released Eclipse 3.2M3 plugins in HEAD.
| + | |
| − | | + | |
| − | We renamed org.eclipse.pde.build_3.2.0/scripts to org.eclipse.pde.build/scripts because our scripts explicitly reference the path to pde build. With the plugin versioning [http://eclipse.org/equinox/documents/plugin-versioning.html changes]
| + | |
| − | now being implemented, we didn't want to change name of pde build each time the qualifier changes. For instance, the full name of the pde.build plugin from from M3 is org.eclipse.pde.build_3.2.0.v20051031a.
| + | |
You betcha! And the Eclipse SDK is such a great environment to work in. We've pumped out quality code by the boat load without a lot of effort.
