Skip to main content
Jump to: navigation, search

Difference between revisions of "LongTermSupport"

(Meeting Minutes)
(Meeting Minutes)
Line 101: Line 101:
* LTS/Polarsys relationship, [ March 27, 2012]
* LTS/Polarsys relationship, [ March 27, 2012]
* LTS Face to face @ EclipseCon, [ March 28, 2012]
* LTS Face to face @ EclipseCon, [ March 28, 2012]
* LTS/Polarsys follow-up, [ March 29, 2012]
* LTS Charter review, [ April 18, 2012]
=Action Tracker=
=Action Tracker=

Revision as of 11:15, 18 April 2012

Long Term Support

Initiative Goals

  1. Enable organisations to collaborate when providing support and maintenance for Eclipse technologies
  2. Enable support and maintenance of Eclipse technologies for Long Term (years) and Very Long Term (decades) durations.


  1. Develop a business model to support the Long Term Support (LTS) Industry Working Group (IWG) at Eclipse
  2. Actively recruit member organizations to create, nurture, and grow an ecosystem of maintenance and support providing and consuming organizations.
  3. Design, implement, and operate a LTS software development forge
  4. Enable and support the directives assigned by the LTS IWG Steering Committee

Next Meeting

  • Meeting @ EclipseCon, Wednesday March 28, 14:00 to 16:00 Eastern. This session will be in Reston Suites A, on the second floor.


A draft copy of the charter for the LTS program is now available.

LTS Ready Project Definition

In order to be included as part of Long Term Support, a project must be compliant with the LTS Readiness Definition

Value Proposition

Prior to the LTS program, support for Eclipse stopped at the SR2 milestone 8 months after release. Companies with products and services based on this software needed to maintain it themselves. The LTS program enables the following value:

Stop fixing everything yourself

  • Share fix binaries built by others
  • Share code with the latest & greatest fixes integrated

Stop maintaining your own server farms

  • Code repository, Bug tracker, Continuous integration server, Build farm
  • Save on cooling, real estate, power, system administration

Hire maintenance committers

  • Their commit access is tied to employment with you
  • No waiting for a committer election, access is immediate
  • Flexibility to hire/contract developers in lower-cost geographies

On-demand responsiveness

  • Produce company-specific fixes 24x7 on your schedule
  • Builds on demand

Get a good deal

  • Our program shares the infrastruture costs across a wide ecosystem
  • We are a non-profit and operating on a cost-recovery basis

Participation Levels

There are 3 levels of participation in the LTS IWG:

  1. Steering Committee, who have all Premium rights plus control the budget, resources, and direction
  2. Premium, who have all Participating rights, plus access to a rich software production forge including build farm, code repositories, bug tracking system, and more.
  3. Participating, who have access to the downloads site and LTS/VLTS binaries.

All LTS IWG members can participate in meetings. There may be special Steering Committee only meetings.

The public are welcomed and encouraged to participate on the LTS IWG mailing list.

Eclipse Foundation's role

The Foundation is not a service provider. Rather it works to cultivate a vibrant ecosystem of Maintenance and support providers and consumers.

The Eclipse Foundation also provides the infrastructure for the code repositories, bug trackers, build farms, test farms, software signing, intellectual property management, and governance in order to manage the projects. It is the trusted vendor neutral organization doing the drudge-work so that others do not have to.

Contact information

Mailing list

Join our Discussion list

LTS Bugs in Bugzilla

See a list of Bugs

Contact person

In time, we will have a steering committee and chair. In the meantime, please contact Andrew Ross - +1 613 614 5772, Skype: rossand2002

Information archive

Mailing list Archive

Mailing list archive

Related Links

Common Build Infrastructure

There is a strong link between this program and the Common Build Infrastructure (CBI). We recognize that the LTS program must support multiple built systems. However, encourage projects to use the CBI to benefit from shared development and expertise in build technologies.

Meeting Minutes

Action Tracker

  • Update Charter based on Feb.2012 business model - Andrew [DONE]
  • LTS IWG participation agreement - Mike/Janet [Draft being reviewed]
  • Identify chair, initiating strategic member

Back to the top