Eclipse, OSGi, Galileo and Release Trains

Ah, Eclipse Galileo is finally out for Friends of Eclipse, I just got the glorious email:

friendofeclipse 300x225 Eclipse, OSGi, Galileo and Release Trains

If we look at the annual releases of Eclipse, we have some nice consistency:

galileodates 300x204 Eclipse, OSGi, Galileo and Release Trains

2004 – June 28th (Eclipse 3.0)
2005 – June 28th (Eclipse 3.1)
2006 – June 30th (Callisto)
2007 – June 29th (Europa)
2008 – June 25th (Ganymede)
2009 – June 24th (Galileo)

Can’t say that about many software projects as large as Eclipse!

With Eclipse releasing at the same time every year, I can say with confidence that we’ll see the next annual release of Eclipse (Helios) on June 24th, 2010. But why do this every year? Why get a bunch of independently run projects to release together?

Well, I think it’s simple… it helps spur the adoption of Eclipse technology. The consumers of Eclipse technology use many projects, not just the “Platform” projects so having the ability to get them at once is a good thing. Essentially, the latency between independently run projects is removed by having an annual release train. Another interesting benefit of having an annual release is that it allows for alignment of version compatibility which is hard to get right. There are many other reasons, but the important thing in my opinion is seeing many developers united around platform and building cool technology with it.

In the end, I’ve convinced myself that having these large annual releases of inter-dependent but independently run projects is only possible because of OSGi and modularity. OSGi allows for fences (API contracts) to be built around useful bits of functionality. As the saying goes, good fences make for good neighbors… and for good release trains.

Enjoy Galileo and see you next year for the Eclipse Helios release :)!

5 Responses to “Eclipse, OSGi, Galileo and Release Trains”

  1. David Carver says:

    I’ll have to disagree on one point…OSGI isn’t the reason that this works. It’s the commitment by the commiters, projects, and others that actually do the work that makes it work.

  2. DR says:

    The Eclipse Foundation should distill the process used to achieve this release train and publish a book of large scale project management. There is a hell of a lot to learn from this!

  3. David, I agree with you that commitment is important.

    However, I think OSGi makes it possible for something of this scale with projects projects that are inter-dependent and independently run. If OSGi or some other strong module system wasn’t in the picture, I don’t think it would be possible to ship something so large and inter-dependent… but hey, that’s my opinion ;)

  4. Nitin Dahyabhai says:

    True, but none of this would have any importance without the community continually pushing us forward.

    And wouldn’t Helios be expected June 23rd, not the 24th?

  5. Oh I completely agree that the dedication of Eclipse committers is the backbone of Eclipse.

    The success of Eclipse rides on the shoulders of Eclipse committers which do a fantastic job every year.

5 responses so far

Written by . Published in Categories: Planet Eclipse