View source for Galileo Simultaneous Release

<div style="border: thin solid black; background-color: #F4FFF4; margin: 3px"><div style="margin: 4px">
This page is for '''developers''' of the June 2009 Galileo Simultaneous Release. Note that [http://www.eclipse.org/projects/galileo.php the master page on the eclipse.org site] points here.
</div></div>

{{Succession Box|
 before=[[Ganymede]]|
 title=Galileo|
 years=2009|
 after=[[Helios]]
}}

===Project Plan===
A roll up project plan for projects participating in the Galileo [[Simultaneous Release]] is found here: http://www.eclipse.org/projects/project-plan.php?projectid=galileo

===Requirements For Participation===
Projects that are part of Galileo agree to abide by the following requirements. '''Note:''' the EMO will remove projects that do not meet the ''required'' constraints.

For a report of overall Galileo status, see this [http://www.eclipse.org/projects/galileo_status.php report].  '''Note:''' this report is bugzilla intensive, so please use sparingly.

==== Must Do ====
{| border="1" cellpadding="3" cellspacing="1"
|+ '''Galileo Release "Must Do" Items'''
! style="background:#efefef;" | Category
! style="background:#efefef;" | Item
! style="background:#efefef;" | Description
! style="background:#efefef;" | Target Milestone
! style="background:#efefef;" | Verification Method
! style="background:#efefef;" | Master Bug
|-
| rowspan="6" | Participation
| rowspan="2" | Intent
| Projects must have stated and demonstrated their intent to join Galileo by the M4+0 date. Projects do so by adding themselves to bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=251715 251715] and asking to have their project-specific bugs created as clones of each of those referenced in this table.
| align="center" | M4
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=251715 251715]
|-
| Projects must have an project plan in [http://wiki.eclipse.org/Development_Resources/Project_Plan XML format].
| align="center" | M4
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252790 252790]
|-
| Communicate
| At least one person from each project must subscribe to cross-project bug inbox, i.e. edit Bugzilla prefs to watch "cross-project.inbox@eclipse.org". Build team members (or their designated alternates) from each project will provide communication channels: phone, mail, IM, IRC and will be available during the milestone integration periods.
| align="center" | M4
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252789 252789]
|-
| Attendance
| Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved.
| align="center" | M4
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252791 252791]
|-
| Ramp Down Policy
| Projects must have a written ramp down policy by M6+0, linked in the table above pending inclusion of ramp down element in the XML project plan. (One of the issues identified with this guideline is that its not so much the ramp down policy of how many votes are needed for each bug fix that we need to be consistent on, but rather the meaning of each of the milestones and release candidates. See [http://www.eclipse.org/eclipse/development/freeze_plan_3.4.php Platform 3.4 Endgame plan] as a guideline. See also [[Galileo/Final Daze|Galileo Final Daze]].)
| align="center" | M5
| align="center" | Script
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252792 252792]
|-
| IP
| Projects must have their IP approved (a normal Eclipse requirement) and will follow the Eclipse Legal deadlines to do so. See also {{bug|220977}}.
| align="center" | CQs submitted by M5, completed by RC3
| align="center" | Manual (Legal)
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252793 252793]
|-
| rowspan="2" | Development
| APIs
| Projects should leverage only published APIs of dependencies.  As a Release Review requirement, all deviations must be documented. Additionally, rectification for the issues should be listed as part of a migration plan, with bugs listed where APIs need to be provided by dependent projects.  '''Perhaps a '99 44/100% Pure APIs' indicator for projects with no improper usage can be used to advertise the 'cleanest' projects?''' ;)
| align="center" | M6
| align="center" | [http://www.eclipse.org/pde/pde-api-tools/ PDE API Tools]
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252794 252794]
|-
| Message Bundles
| Projects must use Eclipse message bundles unless there are technical reasons not to. (see [[Message Bundle Conversion Tool]] and [http://www.eclipse.org/eclipse/platform-core/documents/3.1/message_bundles.html])
| align="center" | M4
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252795 252795]
|-
| rowspan="5" | Bundles
| Version Numbering
| Projects must use 4-part [[Version Numbering|version numbers.]]
| align="center" | M5
| align="center" | Manual (script?)
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252796 252796]
|-
| Leverage OSGi
| All plug-ins (bundles) must use the true bundle form. That is, provide a manifest.mf file, and not rely on the plugin.xml file being 'translated' into a manifest.mf file at initial startup. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130598 bug 130598]. With that, empty plugin.xml files in the presence of a manifest.mf file should not be included in a bundle.
| align="center" | M5
| align="center" | Manual (script?)
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252797 252797]
|-
| Execution Environment
| All plug-ins must correctly list their required JVM versions in the manifest.mf. See the wiki page about selecting the correct JVM [http://wiki.eclipse.org/index.php/EMF_2.3_JVM_Requirements#Runtime_.2F_Compilation_Compatibility].
| align="center" | M5
| align="center" | Manual (script?)
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252798 252798]
|-
| Signing
| Projects must use [[Modeling_Project_Releng/Building/Signing_And_Packing|signed plugins]] using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons.
| align="center" | M4
| align="center" | Script
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252799 252799]
|-
| Use Jars
| Projects must use jar'ed plug-ins (with unpack=false) unless authorized by the planning council for technical reasons. Nested jars should be avoided if possible since it creates problems for projects that has dependencies to such plug-ins. The OSGi runtime is fine with it but the compiler is not able to handle classpaths that contain nested jars. In case only one nested jar exists, it is often better to expand the contents of that jar into the root folder (i.e. unnest the jar). If a plug-in contains large files that are frequently used (opened and closed), a jar'ed plug-in might degrade performance significantly since the file must be decompressed each time it is opened.
| align="center" | M4
| align="center" | Manual (script?)
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252800 252800]
|-
| rowspan="4" | Releng
| Builds
| Projects must have build process maturity: scripted, repeatable, and executable by others.
| align="center" | M4
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252801 252801]
|-
| Orbit
| Any new third-party plug-ins that are common between projects must be consumed via [http://www.eclipse.org/orbit/ Orbit]; the final Galileo release will not have duplicate third-party libraries (note that this only applies to identical versions of the libraries; thus if project A requires foo.jar 1.6 and project B uses foo.jar 1.7, that's ok).
| align="center" | M4
| align="center" | Manual &amp; Script
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252803 252803]
|-
| Optimization
| Projects must [[Update_Site_Optimization|optimize]] their own update site using [[Pack200|pack200]] to reduce bandwidth utilization and provide a better update experience for users. With the introduction of p2, project update sites must generate metadata (artifact and content repository info).
| align="center" | M4
| align="center" | Script
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252804 252804]
|-
| New &amp; Noteworthy
| Must have [[Architecture Council/New and Noteworthy|New &amp; Noteworthy]] for each milestone. Must be something readable and usable not just a static list of all the bugs, e.g. [http://download.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/whatsnew3.4/eclipse-news.html platform]. Corollary: individual new &amp; noteworthy should be linked in to the collective New & Noteworthy.
| align="center" | RC
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252805 252805]
|- 
| rowspan="5" | Deployment
| Work Together
| This means that users can load any subset of the Galileo projects into Eclipse and each of the loaded projects will pass all the same tests as if it had been loaded independently. If such a problem is identified, the affected projects must fix the problem.
| align="center" | RC
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252806 252806]
|- 
| Capabilities
| Each project will provide basic capability/activity definitions to allow for their UI contributions to be hidden.  These must be provided in a separate plugin/feature to facilitate inclusion/exclusion by consumers in product development.
| align="center" | M6
| align="center" | [[Galileo_Capabilities|Manual]]
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252807 252807]
|- 
| rowspan="2" |  Localization
| The project participates in Babel, meaning it is registered and available for string translation, etc.
| align="center" | M6
| align="center" | Script
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252808 252808]
|-
| Must use [[ICU4J | ICU4J]].
| align="center" | M5
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252809 252809]
|-
| Branding
| Each major project (as determined by participating PMCs) should have an About dialog icon with [https://bugs.eclipse.org/bugs/show_bug.cgi?id=198941 descriptive text] (e.g. provider name = "Eclipse Modeling Project" and not simply Eclipse.org) and contribute to the welcome page.
| align="center" | RC
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252813 252813]
|}

==== Should Do ====
{| border="1" cellpadding="3" cellspacing="1"
|+ '''Galileo Release "Should Do" Items'''
! style="background:#efefef;" | Item
! style="background:#efefef;" | Description
! style="background:#efefef;" | Target Milestone
! style="background:#efefef;" | Verification Method
! style="background:#efefef;" | Master Bug
|-
| Usability
| Should follow the [[User Interface Guidelines]].  The [[UI Checklist]] is a good place to start.  Also, should participate in a [[User Interface Best Practices Working Group]] [[UIBPWG UI Walkthrough | UI walkthrough]].
| align="center" | M5
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252810]
|-
| Accessibility
| Should design and test for accessibility.
| align="center" | M4
| align="center" | [http://www.eclipse.org/actf/ ACTF]
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252811]
|-
| Performance
| Projects should devote at least one milestone to performance and scalability improvements.
| align="center" | M7
| align="center" | [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.test.performance/doc/Performance%20Tests%20HowTo.html?view=co]
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252812]
|- 
| rowspan="3" | Localization
| The project should use the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339 Babel Pseudo Translation Test] to verify their translatablity.
| align="center" | M6
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252814]
|-
| Should freeze the UI sufficiently early to allow the Babel project time to translate strings.
| align="center" | M6
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252815]
|-
| Should design and test for enabling all languages including bidi, unicode characters, etc.
| align="center" | M7
| align="center" | Manual
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252816]
|}

===Milestones and Release Candidates===
These milestone and release candidate dates are based on the dependencies of the projects (we call these the +0, +1, and +2 dependencies). Obviously, if a +0 date slips, then it will cause the +1 and +2 dates to slip; similarly for a +1 slip causing +2 slips.  Note that the +0, +1, +2, and +3 dates are roughly equivalent to stable nightly builds in a traditional Eclipse project - each of these partial milestone builds will incorporate more and more of the associated project milestones. The "Release" date is the official M/RC date. 

Note: in the following table, '''''RC5''''' on the 'Galileo' line does not mean this final build is a release ''''candidate'''' ... it is still to be the ''''final build'''' for this Release ... but 'RC5' is the suggested "target" to have some consistent terminology in Bugzilla, and similar things, to be able to mark things that are different in the final release build than in the RC4 build. [The full word, "Galileo" doesn't make a very good bugzilla milestone target, since it's a little too inclusive, and "R" (for "Release") is too short. TODO: next year consider "GA" for this final target?]  

'''Hopefully''' there will '''not by ''ANY'' differences''' between RC4, and RC5 ... but, some projects may find they have to make doc additions, readme files, etc., so ... this just provides a way that such changes can be consistently marked, tracked, etc., to better keep everyone informed about what might be different between RC4 and the RC5 (the final released code). [Note: it's probably obvious, but this does not mean "RC5" should be part of the final zip file names or anything. those can still be what ever "final" name they would always have.]

<googlecalendar width="100%" title="Helios Release Schedule">gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com</googlecalendar>

The calendar is available in the following formats:
[http://www.google.com/calendar/ical/gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com/public/basic.ics ICal],[http://www.google.com/calendar/feeds/gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com/public/basic ATOM News Feed],[http://www.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York HTML]

===Communication===

====Cross-Project Milestone & RC Status Reporting====
<del>
As with Ganymede, reporting on status will be done using a wiki table.
</del>

We have decided that instead of affirmative signoffs, projects should post exceptions to the cross-project dev mailing list.

====Conference Calls====

The [[Planning Council]] is the body responsible for coordinating the Galileo release train.  Thus, its [[Planning_Council#Call_and_Meeting_Schedule|conference calls]] are the Galileo 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. Galileo, although not a "project" per se, will use the same structure:
* [https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev cross-projects-issues-dev] - mailing list for developers and releng (see  [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/threads.html archives])
* [http://www.eclipse.org/newsportal/thread.php?group=eclipse.simultaneous-release eclipse.simultaneous-release] - newsgroup for users (see [http://dev.eclipse.org/newslists/news.eclipse.simultaneous-release/maillist.html archives])

The old [https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council eclipse.org-planning-council ] mailing list will be used for non-Galileo Planning Council items.

=== Bugs & Feature Requests ===

* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse+Foundation&product=Community&component=Cross-Project&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Search] in Eclipse Foundation > Community > Cross-Project
* Open a new [https://bugs.eclipse.org/bugs/enter_bug.cgi?assigned_to=cross-project.inbox%40eclipse.org&product=Community&component=Cross-Project Cross-Project] bug

===Galileo Builds and P2 repository ===

A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08 and now Galileo '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 [[Galileo/Build | Galileo Build]] page (with old information on the [[Ganymede/Build | Ganymede Build]]  and [[Europa/Build | Europa Build]] pages).

And with Galileo we are using the [[Buckminster Galileo Builder]].

The [[Galileo/Contributing_to_Galileo_Build | Contributing to Galileo Build]] page is where you go to learn how to add your project to the Galileo build.

==== p2 Repository ====

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

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

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 [[Ganymede#Coordinated_Service_Releases| 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. 

{| border="1" align="center" width="600"
|-
| 
! +0 <br> Mon. 
! +1 <br> Tues. 
! +2 <br> Wed. 
! +3 <br> Thur. 
! EPP <br> Fri.
|-
! align="right" | RC1
| 8/10
| 8/11
| 8/12
| 8/13
| 8/14
|-
! align="right" | RC2
| 8/31
| 9/1
| 9/2
| 9/3
| 9/4
|-
! align="right" | RC3
| 9/7
| 9/8
| 9/9
| 9/10
| 9/11
|-
! align="right" | RC4
| 9/14
| 9/15
| 9/16
| 9/17
| 9/18
|-
! align="right" | Galileo SR1 ("GA")
| 
| 
| 
| promote: 9/24
| GA: 9/25
|}

==== SR2 ====
2/26/10 (last Friday of February)

Rampdown similar to SR1.


{| border="1" align="center" width="600"
|-
| 
! +0 <br> Mon. 
! +1 <br> Tues. 
! +2 <br> Wed. 
! +3 <br> Thur. 
! EPP <br> Fri.
|-
! align="right" | RC1
| 1/18
| 1/19
| 1/20
| 1/21
| 1/22
|-
! align="right" | RC2
| 2/1
| 2/2
| 2/3
| 2/4
| 2/5
|-
! align="right" | RC3
| 2/8
| 2/9
| 2/10
| 2/11
| 2/12
|-
! align="right" | RC4
| 2/15
| 2/16
| 2/17
| 2/18
| 2/19
|-
! align="right" | Galileo SR2 ("GA")
| 
| 
| 
| promote: 2/25
| GA: 2/26
|}

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

{| border="1" align="center" cellpadding="3" cellspacing="1"
! Project/''Component'' 
! Project/''Component'' Lead(s) 
! Release Engineer
! Offset 
! Ramp down Policy
|-
|
[http://www.eclipse.org/actf/ Accessibility Tools Framework (ACTF)]
|| Chieko Asakawa|| Kentarou Fukuda || +3 || [http://www.eclipse.org/projects/project-plan.php?projectid=technology.actf#rampdown ACTF Ramp-down]
|-
| 
[http://www.eclipse.org/birt Business Intelligence and Reporting Tools (BIRT)]
|| Wenfeng Li || Xiaoying Gu || +2 || [[BIRT2.5_Rampdown_Policy | BIRT Ramp-down Policy for Galileo]]
|-
| 
[http://www.eclipse.org/buckminster  Buckminster]
|| Thomas Hallgren, Henrik Lindberg || Thomas Hallgren || +2 || [[Buckminster/Galileo_Ramp-Down_Policy|Buckminster Ramp-down]]
|-
| 
[http://www.eclipse.org/cdt CDT]
|| Doug Schaefer || Vivian Kong || +1 || [[CDT/planning/5.0rampdown | CDT 5.0 Ramp-down]]
|-
| 

[http://www.eclipse.org/dltk DLTK]
|| Andrey Platov || Andrey Platov || +3 || [[DLTK/Ramp_Down_Policy-1.0|DLTK 1.0 Ramp Down Policy]]
|-
|

<strike>[http://www.eclipse.org/dsdp/ DSDP] [http://www.eclipse.org/dsdp/dd/ DD]</strike>
|| <strike>Pawel Piech</strike> || <strike>Ted Williams</strike> || <strike>+2</strike> || <strike>[[DSDP/DD/DD_1.0_RampDownPolicy|DD Ramp-down]]</strike>
|-
| 
[http://www.eclipse.org/dsdp/ DSDP] [http://www.eclipse.org/dsdp/tm/ TM]
|| Martin Oberhuber || Martin Oberhuber || +1 || [[DSDP/TM/3.1_Ramp_down_Plan|TM Ramp-down]]
|-

| 
[http://www.eclipse.org/dsdp/ DSDP] [http://www.eclipse.org/dsdp/tml/ TmL]
|| Eric Cloninger, Fabio Fantato || Fabio Fantato || +0 || [[DSDP/TML/RampdownPlan_Galileo|TmL Ramp-down]]
|-

|

[http://www.eclipse.org/dsdp/ DSDP] [http://www.eclipse.org/dsdp/mtj/ MTJ]
|| Gustavo de Paula || Diego Madruga Sandin || +1 || [[DSDP/MTJ/MTJ_1.0_Ramp_Down_Plan|MTJ Ramp-down]]
|-
| 
 
[http://www.eclipse.org/datatools/ Data Tools Platform (DTP)]
|| Brian Fitzpatrick || Xiaoying Gu || +1 || [[DTP Galileo Rampdown Policy|DTP Ramp-down]]
|-
|

[http://www.eclipse.org/ecf/ Eclipse Communication Framework (ECF)]
|| Scott Lewis || Ted Kubaska/Scott Lewis || +2 || [[ECF_3.0.0/Galileo_Ramp-Down_Policy | ECF Ramp-down]]
|-
|
[http://www.eclipse.org/eclipselink/ Eclipse Persistence Services Project (EclipseLink)]
|| Peter Krogh, Doug Clarke|| Peter Krogh || +1 || [[EclipseLink/Development/Galileo_Ramp_Down | EclipseLink Ramp Down]]
|-
| 
[http://www.eclipse.org/eclipse/ The Eclipse Project]
:''[http://www.eclipse.org/platform Platform], [http://www.eclipse.org/jdt JDT], [http://www.eclipse.org/pde PDE]''
|| Mike Wilson || Kim Moir<br/>[http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html Build Schedule] || 0 || [http://www.eclipse.org/eclipse/development/freeze_plan_3.5.php Eclipse 3.5 Endgame plan]
|-
| 
[http://www.eclipse.org/Equinox/ Equinox]
|| Thomas Watson, Jeff McAffer || Kim Moir<br/>[http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html Build Schedule] || 0 || [http://www.eclipse.org/equinox/planning/freeze_plan_3.5.php Equinox 3.5 Endgame plan]
|-
| 
[http://www.eclipse.org/emf/ EMF]
:''[http://www.eclipse.org/modeling/emf/?project=emf#emf EMF (Core)]''
:''[http://www.eclipse.org/modeling/emf/?project=query#query Query], [http://www.eclipse.org/modeling/emf/?project=transaction#transaction Transaction], [http://www.eclipse.org/modeling/emf/?project=validation#validation Validation],
:''[http://www.eclipse.org/modeling/emft/?project=teneo#teneo Teneo]''
:''[http://www.eclipse.org/modeling/emft/?project=net4j#net4j Net4j]'', ''[http://www.eclipse.org/modeling/emft/?project=cdo#cdo CDO]''
|| Ed Merks
:''Ed Merks''
:''Christian Damus''
:''Martin Taal'' 
:''Eike Stepper''
|| <br>
:''Nick Boldt''
:''Christian Damus''
:''Martin Taal'' 
:''Eike Stepper''
|| <br/>
+1<br/>
+2<br/>
+2<br/>
+1, +2
||[[Modeling_Project_Ramp_Down_Policy/Galileo|Modeling Project<br/>Ramp-down]]
|-
|

[http://www.eclipse.org/modeling/emft EMFT]
:''<strike>[http://www.eclipse.org/emft/projects/search/ EMF Search]</strike>''
:''[http://www.eclipse.org/emft/projects/compare/ EMF Compare]''
:''[http://www.eclipse.org/modeling/emft/?project=ecoretools Ecore Tools]''
:''[http://www.eclipse.org/modeling/emft/?project=mint#mint Mint]''
:''[http://www.eclipse.org/modeling/emft/?project=mwe MWE]''
|| Ed Merks
:''<strike>Lucas Bigeardel</strike>'' 
:''Cédric Brun'' 
:''David Sciamma'' 
:''Peter Nehrer''
:''Bernd Kolb''
|| <br/>
:''<strike>Lucas Bigeardel</strike>''
:''Cédric Brun''
:''Jacques Lescot''
:''Peter Nehrer''
:''Dennis Huebner''
|| <br/>
+2
||[[Modeling_Project_Ramp_Down_Policy/Galileo|Modeling Project<br/>Ramp-down]]
|-
|

[http://www.eclipse.org/epp/usagedata EPP]
|| Markus Knauer
:''Wayne Beaton'' 
|| 
Wayne Beaton
|| +2
|| [http://wiki.eclipse.org/EPP/Galileo_Ramp-Down_Policy EPP Ramp Down Policy]
|-
|

[http://www.eclipse.org/gef/ Graphical Editing Framework (GEF)]
|| Anthony Hunter || Anthony Hunter || +1 ||
[http://www.eclipse.org/gef/plan/gef_plan_3_4.php#RampDown GEF 3.4 Ramp-Down]
|-
| 

[http://www.eclipse.org/gmf/ Graphical Modeling Framework (GMF)]
|| Richard Gronback || Richard Gronback || +2 || [[Modeling_Project_Ramp_Down_Policy/Galileo|Modeling Project<br/>Ramp-down]]
|-
| 

[http://www.eclipse.org/jwt/ JWT]
|| Marc Dutoo, Florian Lautenbacher || Mickael Istria || +3 || [[JWT Ramp-Down-Policy|JWT Ramp-Down]]
|-
|
[http://www.eclipse.org/mat/ Memory Analyzer (MAT)]
|| Andreas Buchen || Erwin Margewitsch || +3 || 
|-
| 

[http://www.eclipse.org/modeling/mdt/ MDT]
:''[http://www.eclipse.org/modeling/mdt/?project=ocl#ocl OCL]''
:''[http://www.eclipse.org/modeling/mdt/?project=uml2#uml2 UML2]''
:''[http://www.eclipse.org/modeling/mdt/?project=uml2tools#uml2tools UML2 Tools]''
:''[http://www.eclipse.org/modeling/mdt/?project=xsd#xsd XSD]''
|| Kenn Hussey
:''Aleksandr Igdalov''
:''James Bruck''
:''Michael Golubev''
:''Ed Merks''
|| <br>
:''Aleksandr Igdalov''
:''James Bruck''
:''Michael Golubev''
:''Nick Boldt''
||<br/>
+1<br/>
+1<br/>
+3<br/>
+1
| rowspan="3" | [[Modeling_Project_Ramp_Down_Policy/Galileo|Modeling Project<br/>Ramp-down]]
|-
| 
[http://www.eclipse.org/m2m/ M2M]
:''[http://www.eclipse.org/m2m/atl/ ATL]''
:''[http://wiki.eclipse.org/index.php/QVTO QVTO]''
|| Frédéric Jouault
:''Frédéric Jouault''
:''Radek Dvorak''
|| <br/>
:''William Piers''
:''Radek Dvorak''
|| &nbsp;
+2
|-
| 
[http://www.eclipse.org/modeling/m2t/ M2T]
:''[http://www.eclipse.org/modeling/m2t/?project=jet#jet JET]''
:''[http://www.eclipse.org/modeling/m2t/?project=xpand Xpand]''
:''[http://www.eclipse.org/modeling/m2t/?project=acceleo Acceleo]''
|| Paul Elder
:''Paul Elder''
:''Sven Efftinge''
:''Jonathan Musset'
|| <br>
:''Paul Elder''
:''Dennis Huebner''
:''Cédric Brun''
|| <br>
+1<br/>+2<br/>+2
|-
|
[http://www.eclipse.org/mylyn/ Mylyn]
|| Mik Kersten || Steffen Pingel || +3 ||
[http://www.eclipse.org/projects/project-plan.php?projectid=tools.mylyn#release_milestones Ramp Down]
|-
|
[http://www.eclipse.org/pdt/ PHP Development Tools (PDT)]
|| Roy Ganor|| Roy Ganor
:''Nick Boldt (backup)''
|| +3 || 
|-
|
[http://www.eclipse.org/rap/ Rich Ajax Platform (RAP)]
||Jochen Krause, Ruediger Herrmann
|| Ralf Sternberg, Ruediger Herrmann
|| +2 
||[[RAP/Ramp down Galileo|RAP Ramp down]]
|-
|
[http://www.eclipse.org/riena/ Riena]
|| Christian Campo || Christian Campo || +3 || [[Riena_Project/Plan/1.1#Ramp_Down|Ramp down]]
|-
|
[http://www.eclipse.org/stp/ SOA Tools Platform (STP)]
:''[http://www.eclipse.org/stp/sca/ SCA Tools]''
:''[http://www.eclipse.org/bpmn/ BPMN]''
||Oisin Hurley 
:''Stéphane Drapeau''
:''Antoine Toulmé''
||Oisin Hurley <br/>
:''Stéphane Drapeau
:''Antoine Toulmé
|| +3 || [[STP/Galileo2009/RampDown|Ramp-down]]
|-
|
[http://www.eclipse.org/subversive/ Subversive]
||Igor Vinnykov || Igor Burilo || +2 ||
[http://wiki.eclipse.org/Subversive_Ramp_Down_Galileo Ramp-down]
|-
|
[http://www.eclipse.org/swordfish/ Swordfish]
|| Oliver Wolf || Oliver Wolf || +3 || 
[[Swordfish/Ramp_down_Galileo|Ramp-down]]
|-
|
[http://www.eclipse.org/modeling/tmf/ TMF]
:''[http://www.eclipse.org/modeling/tmf/?project=xtext Xtext]''
|| Sven Efftinge, Frédéric Jouault
:''Sven Efftinge''
|| <br>
Dennis Huebner
|| <br>
+2
||[[Modeling_Project_Ramp_Down_Policy/Galileo|Modeling Project<br/>Ramp-down]]
|-
|
[http://www.eclipse.org/tptp/ Test & Performance Tools Platform (TPTP)]
:''Platform, Test, Trace, Monitoring''
|| Kathy Chan || Joel Cayne || +2 || [http://wiki.eclipse.org/index.php/TPTP_Project_Ramp_Down_Policy_for_Galileo Policy]
|-
|
[http://www.eclipse.org/webtools/ Web Tools Platform (WTP)]
|| David Williams || David Williams || +2 || [[WTP 3.1 Ramp down Plan for Galileo]]
|-
|}

[[Category:Galileo]] [[Category:Coordinated]]