Jump to: navigation, search

Helios/Simultaneous Release Plan

This page is for developers of the June 2010 Helios Simultaneous Release. If you are a consumer of the Release, perhaps a tester or an early adopter, you'll want Helios Simultaneous Release For Users. Note that the master page on the eclipse.org site points here.

This page is under development. It is expected to be complete around Mid September.


Project Plan

A roll up project plan for projects participating in the Helios simultaneous release is found here: http://www.eclipse.org/projects/project-plan.php?projectid=helios

Requirements For Participation

Projects that are part of Helios agree to abide by the requirements of the Eclipse Yearly Release.

[TBD: link to report]

Milestones and Release Candidates

The milestone dates are at roughly 6 week intervals. Any end-of-cycle release-candidate (RC) dates are typically one week apart. Each project has their deliveries due at times offset from the end-date, so that the project dependencies can come together in a reasonable order. These delivery times are based on the dependencies between projects -- they are called the +0, +1, +2, and +3 dependencies. Projects themselves decide if they are +0, +1, +2, or +3. The actual time-offset represented by these intervals change over the course of the year of development, being several days at first, but then only one day near the end of the release. The following calendar is the official schedule of the overall Helios Release. Projects are free to have their own schedules as long as they meet the Helios deliverables.

Note that projects choose their +n category based on major or primary dependencies. There are many cases a project might have to deliver pieces of their code a little earlier, if some project depends on it. These sorts of deviations are left the the projects to work out among themselves.

TODO: final "target" to be called "GA", not RC5.


The calendar is available in the following formats: ICal,ATOM News Feed,HTML

Communication

Cross-Project Milestone & RC Status Reporting

It is essential for many aspect of the simultaneous release that communication be prompt and clear, on many topics. One of the most important ones, is if someone is not meeting some date or delivery. Put another way, we assume everyone is on target and has delivered their stuff unless a note is sent to cross-project list that you are delayed.

Conference Calls

The Planning Council is the body responsible for coordinating the Helios release train. Thus, its conference calls are the Helios planning and coordination calls.

Mailing Lists and Newsgroups

Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. While Helios is not a "project" per se, it will use the same structure:

Developer mailing list
  • cross-projects-issues-dev - mailing list for developers and releng (see archives). This is the list to use to discuss build issues, announce changes in plans, slippage in deliverables, etc.
Users news group
Bugzilla

The old eclipse.org-planning-council mailing list will be used for non-Helios Planning Council items.

Bugs & Feature Requests

Helios Builds and P2 repository

A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08 and now Helios '09 builds. These are available in their own CVS respository. You can find more information about how this is organized and individual project responsibilities for the build on this Helios Build page (with old information on the Ganymede Build and Europa Build pages).

And with Helios we are using the Buckminster Helios Builder.

The Contributing to Helios Build page is where you go to learn how to add your project to the Helios build.

p2 Repository

To obtain the latest published bits from Helios, use this URL:

http://download.eclipse.org/releases/helios

It contains the latest milestone, release candidate, eventually the release itself, and then eventually service releases.

To obtain the latest working version, as we build up to a milestone or release, you can test the site at

http://download.eclipse.org/releases/staging

Coordinated Service Releases

SR1

GA: 9/25/09 (last Friday of September)

In the SR1 rampdown, as shown in the following table, there will be 4 RCs, each spanning one week, with projects staging themselves into the build just one day apart.

Projects may elect not to participate in a particular RC, but have an obligation to fix any build problems that is related to their code or p2 repository.

RC1 will be in the middle of August, several weeks earlier than previous years, just to make sure we can still build, etc. Subsequent RCs dates are similar to previous years, except a "quiet" final week is also planned. (It is normally pretty quiet anyway ... this just formalizes it).

The Final week before GA will not have any further builds or contributions, but instead be reserved for final adopter testing and preparation and only emergency fixes for very serious regressions will be considered.

The 'promote' day (9/24) will be the day projects put final zips in their final spot (without displaying them) so they can propagate through the mirroring system. Similar for the p2 repository -- it will be replaced on 9/24 with the new content so it can start mirroring. Note: there is no plan to retain multiple versions in the common discovery repository (unless someone volunteers to do what's required to make that happen). At noon on 9/25 projects can make their final maintenance releases visible.

+0
Mon.
+1
Tues.
+2
Wed.
+3
Thur.
EPP
Fri.
RC1 8/10 8/11 8/12 8/13 8/14
RC2 8/31 9/1 9/2 9/3 9/4
RC3 9/7 9/8 9/9 9/10 9/11
RC4 9/14 9/15 9/16 9/17 9/18
Helios SR1 ("GA") promote: 9/24 GA: 9/25

SR2

2/26/10 (last Friday of February)

Rampdown similar to SR1.


+0
Mon.
+1
Tues.
+2
Wed.
+3
Thur.
EPP
Fri.
RC1 1/18 1/19 1/20 1/21 1/22
RC2 2/1 2/2 2/3 2/4 2/5
RC3 2/8 2/9 2/10 2/11 2/12
RC4 2/15 2/16 2/17 2/18 2/19
Helios SR2 ("GA") promote: 2/25 GA: 2/26

Projects

The projects that plan to participate in the Helios Simultaneous Release are listed below, along with their milestone offsets, leaders, release engineer, and ramp down policy.

Project/Component Project/Component Lead(s) Release Engineer Offset Ramp down Policy

Accessibility Tools Framework (ACTF)

Chieko Asakawa Kentarou Fukuda +3 ACTF Ramp-down

Business Intelligence and Reporting Tools (BIRT)

Wenfeng Li Xiaoying Gu +2 BIRT Ramp-down Policy for Helios

Buckminster

Thomas Hallgren, Henrik Lindberg Thomas Hallgren +2 Buckminster Ramp-down

CDT

Doug Schaefer Vivian Kong +1 CDT 5.0 Ramp-down

DLTK

Andrey Platov Andrey Platov +3 DLTK 1.0 Ramp Down Policy

DSDP DD

Pawel Piech Ted Williams +2 DD Ramp-down

DSDP TM

Martin Oberhuber Martin Oberhuber +1 TM Ramp-down

DSDP TmL

Eric Cloninger, Fabio Fantato Fabio Fantato +0 TmL Ramp-down

DSDP MTJ

Gustavo de Paula Diego Madruga Sandin +1 MTJ Ramp-down

Data Tools Platform (DTP)

Brian Fitzpatrick Xiaoying Gu +1 DTP Ramp-down

Eclipse Communication Framework (ECF)

Scott Lewis Ted Kubaska/Scott Lewis +2 ECF Ramp-down

Eclipse Persistence Services Project (EclipseLink)

Peter Krogh, Doug Clarke Peter Krogh +1 EclipseLink Ramp Down

The Eclipse Project

Platform, JDT, PDE
Mike Wilson Kim Moir
Build Schedule
0 Eclipse 3.5 Endgame plan

Equinox

Thomas Watson, Jeff McAffer Kim Moir
Build Schedule
0 Equinox 3.5 Endgame plan

EMF

EMF (Core)
Query, Transaction, Validation,
Teneo
Net4j, CDO
Ed Merks
Ed Merks
Christian Damus
Martin Taal
Eike Stepper

Nick Boldt
Christian Damus
Martin Taal
Eike Stepper

+1
+2
+2
+1, +2

Modeling Project
Ramp-down

EMFT

EMF Search
EMF Compare
Ecore Tools
Mint
MWE
EMF Index
Ed Merks
Lucas Bigeardel
Cédric Brun
David Sciamma
Peter Nehrer
Bernd Kolb
Jan Koehnlein

Lucas Bigeardel
Cédric Brun
Jacques Lescot
Peter Nehrer
Dennis Huebner
Dennis Huebner

+2

Modeling Project
Ramp-down

EPP

Markus Knauer
Wayne Beaton

Wayne Beaton

+2 EPP Ramp Down Policy

Graphical Editing Framework (GEF)

Anthony Hunter Anthony Hunter +1

GEF 3.4 Ramp-Down

Graphical Modeling Framework (GMF)

Richard Gronback Richard Gronback +2 Modeling Project
Ramp-down

Generative Modeling Technologies (GMT)

MoDisco
Jean Bezivin
Hugo Bruneliere

Nicolas Bros

+3

Modeling Project
Ramp-down

JWT

Marc Dutoo, Florian Lautenbacher Christian Saad +3 JWT Ramp-Down

Memory Analyzer (MAT)

Andreas Buchen Erwin Margewitsch +3

MDT

OCL
UML2
UML2 Tools
XSD
Kenn Hussey
Aleksandr Igdalov
James Bruck
Michael Golubev
Ed Merks

Aleksandr Igdalov
James Bruck
Michael Golubev
Nick Boldt

+1
+1
+3
+1

Modeling Project
Ramp-down

M2M

ATL
QVTO
Frédéric Jouault
Frédéric Jouault
Radek Dvorak

William Piers
Radek Dvorak
 

+2

M2T

JET
Xpand
Acceleo
Paul Elder
Paul Elder
Sven Efftinge
Jonathan Musset'

Paul Elder
Dennis Huebner
Cédric Brun

+1
+2
+2

Mylyn

Mik Kersten Steffen Pingel +3

Ramp Down

PHP Development Tools (PDT)

Roy Ganor Roy Ganor
Nick Boldt (backup)
+3

Rich Ajax Platform (RAP)

Jochen Krause, Ruediger Herrmann Ralf Sternberg, Ruediger Herrmann +2 RAP Ramp down

Riena

Christian Campo Christian Campo +3 Ramp down

SOA Tools Platform (STP)

SCA Tools
BPMN
Oisin Hurley
Stéphane Drapeau
Antoine Toulmé
Oisin Hurley
Stéphane Drapeau
Antoine Toulmé
+3 Ramp-down

Subversive

Igor Vinnykov Igor Burilo +2

Ramp-down

Swordfish

Zsolt Beothy-Elo, Oliver Wolf Zsolt Beothy-Elo +3

Ramp-down

TMF

Xtext
Sven Efftinge, Frédéric Jouault
Sven Efftinge

Dennis Huebner


+2

Modeling Project
Ramp-down

Test & Performance Tools Platform (TPTP)

Platform, Test, Trace, Monitoring
Kathy Chan Joel Cayne +2 Policy

Web Tools Platform (WTP)

David Williams David Williams +2 WTP 3.1 Ramp down Plan for Helios