Eclipse Kepler Release: By the Numbers
We originally had 72 projects sign up to participate in the Eclipse Juno simultaneous release on June 27/2012. By release day, that number had dropped to 71 with the removal of EMF Query 2 (which has since been terminated). If you scrutinize the table, you may notice that there are 72 entries; last year, the Eclipse project contributed two different releases (3.8 and 4.2). My count correctly includes these both as a single project.
This year for Kepler, the number is again 72.
The composition this year is a little different. Most of the projects from last year’s Juno release have stayed on as part of Kepler. But a handful of projects have decided to drop out of the simultaneous release. Virgo, Jetty, and the Runtime Packaging Project (RTP) have all decided not to participate. The Xtend project merged into Xtext, so it too drops off the list (the bits from Xtend are still part of the simultaneous release as part of Xtext’s contribution).
While Jetty is not formally participating in the simultaneous release, some of the Jetty project’s bits are in the Kepler software repository: they have been pulled in as dependency for one or more projects that are participating in Kepler. For similar reasons, there are bits from the Gemini JPA project in the Kepler software repository. If you find this a bit confusing, you’re in good company.
Some of the projects include subprojects. The Mylyn project contribution to Kepler, for example, is listed as a single entry, but includes Builds, Commons, Context, Docs, Reviews, Tasks, Versions, Model Focused Tools (MFT), and R4E. The Eclipse Project, Web Tools, and Data Tools each also contains a handful of subprojects; and the Parallel Tools Platform’s (PTP) release include Photran. All together, there are 114 (updated) total projects formally contributing something to the release.
Some of the projects don’t actually have code repositories of their own. The Eclipse, Web Tools, Data Tools, and Mylyn top-level projects, for example, do not have their own code. The java development tools (JDT) and Eclipse Platform projects are also, I believe, container projects that do not have their own code repositories (the code is all owned by subprojects). Of the 114 (updated) projects contributing to Kepler, 107 (updated) have their own code repositories. Eight Kepler projects are using Subversion source code repositories. The remaining 99 (updated) use Git (~93% updated).
A total of 428 (updated) committers from 54 different organizations each provided at least one of the 48K (updated) commits that have been made against ~200K files in Kepler project source code repositories in the past year (since June 27/2012). These numbers don’t include the non-participating dependency projects discussed above (e.g. Jetty, and Gemini JPA).
There are 4,786 OSGi bundles and 915 features in the Kepler software repository (as of June 7/2013),
Finally, we estimate that ~58 million lines of code contributed to the the Kepler repository.
Compare this against the Juno numbers.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)