Skip to main content
Jump to: navigation, search

Difference between revisions of "Developer Team Page"

m (Version Numbering)
(Meetings and Events)
Line 7: Line 7:
===Meetings and Events===
===Meetings and Events===
* [[Higgins F2F planning]]
* [[Higgins Past Meetings and Events]]
* [[Higgins Past Meetings and Events]]

Revision as of 11:44, 10 March 2008

Note: This page is relevant only for Higgins committers and active contributors.

Issue Tracking

Meetings and Events

Version Numbering

A Higgins release is a set of components, that are in turn comprised of a set of one or more SVN projects (e.g. a folder containing src for a plugin, C++ lib, jar, etc.). We make a distinction between the version number of an overall Higgins release and the version numbers of constituent projects.

Higgins releases:

  • The next few after 1.0 will be named 1.0.1, 1.0.2, ...
  • We create a new SVN branch for each release of Higgins named consistent with the release number (e.g. R1-0-0 or R1-0-1)
  • We expect to have Higgins releases approx every 6 weeks or so.

SVN projects:

  • Are named major.minor.service.qualifier as described here: Version Numbering
  • If java: have their plugin version numbers updated at least by the time a new Higgins release is created (as described above)

SVN branches

  • HEAD -- ongoing development
  • B1-0-0 -- Higgins 1.0.0 release 2008-2-21
  • B1-0M9 -- at the end of 1.0M9
  • M0-8 -- at the end 1.0M8



  • Higgins Development Processes
  • Component Owners MUST:
    1. Create rows (and sometimes entire tables) for each project on the Components page.
    2. Manually create (and constantly update) the "dep" wiki page in the "Dependencies" column (entitled "Dep.") for each project/row on the Components page.
    3. Edit the autobuild scripts to include java components in the nightly build
    4. Create a "row" wiki page for each row using the Component Description Template
    5. Make sure that automated build scripts are using the latest build.xml
    6. Make sure that all 3rd party dependent jars are read from the dependencies.redistributable project. For projects that autobuild this can be verified by checking that the auto-generated "Third Party Dependencies" section of the "dependencies" page linked from a build page (see the "downloads" column on the Components page.




Misc Tools


Contributions by team members

Eclipse Foundation-related Info

Eclipse Committers



Clarification of IP processes for use of third party libraries

  • Any time anyone working on the Higgins project wants to introduce a project dependency, it needs to be brought forward to the Higgins project.
  • If the decision is made to introduce the dependency and the dependency involves software that is not licensed under the EPL, then a formal IP process needs to be gone though to approve the software binaries for inclusion in the project cvs. Note that this process must be followed even if the software is a common java library used by other Eclipse processes. (If the software has been used by another Eclipse project, the process is much faster.) Eclipse has a system IPzilla for managing this process. If you are anticipating a dependency, you need to bring it forward as soon as possible to allow time for the IP due diligence process to take place. See more about IPzilla below.
  • Libraries licensed with EPL are the easiest to get permission to use, followed by Apache 2.0. GPL and LGPL licences are not compatible with EPL.


  • Orbit is designed to be a repository for third party libraries that are approved for use in Eclipse projects. If the incoming libraries are not already bundles then Orbit committers will work to create a bundle that is suitable for use in Eclipse projects. See for a list or Orbit managed libraries. Orbit managed libaries are the easiest of third party libraries to add to an Eclipse project. Even if a library is listed under Orbit, you still need to go through the IPzilla process before putting it into the Higgins CVS.


Back to the top