Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "E4/Builds"

< E4
(Integration Builds)
(Integration Builds)
Line 1: Line 1:
= Integration Builds =
+
= Builds =
 +
 
 +
== Integration Builds ==
  
 
{| border="1"
 
{| border="1"
Line 10: Line 12:
 
| Weekly
 
| Weekly
 
|}
 
|}
 +
 +
[http://download.eclipse.org/e4/downloads/ e4 Downloads Page]
 +
 +
=== Submitting For the Build ===
 +
 +
Teams should use the "Eclipse Releng Tools" to update their releng project for each build.  The releng tools can be installed from the update sites already included in 3.5.
 +
 +
'''Tags''': tags should be of the form v<date>, so v20081120 or v20081120-1300
 +
 +
'''Versioning Plugins''': Teams should try and follow the standard versioning rules posted at [[Version_Numbering]].  If you need to copy over an existing eclipse project to make changes, please increment the minor number by 100.  i.e. 3.5.0 becomes 3.105.0.  When you need to break API, then update the major number. i.e. 3.105.0 becomes 4.0.0
 +
 +
'''Checking in code''': The checking comment should at a minimum include "bug #", and preferably be of the form "bug # summary"

Revision as of 14:07, 20 November 2008

Builds

Integration Builds

E4 Integration Builds
Date Time Frequency
Thursdays 19:30 EST Weekly

e4 Downloads Page

Submitting For the Build

Teams should use the "Eclipse Releng Tools" to update their releng project for each build. The releng tools can be installed from the update sites already included in 3.5.

Tags: tags should be of the form v<date>, so v20081120 or v20081120-1300

Versioning Plugins: Teams should try and follow the standard versioning rules posted at Version_Numbering. If you need to copy over an existing eclipse project to make changes, please increment the minor number by 100. i.e. 3.5.0 becomes 3.105.0. When you need to break API, then update the major number. i.e. 3.105.0 becomes 4.0.0

Checking in code: The checking comment should at a minimum include "bug #", and preferably be of the form "bug # summary"

Back to the top