DSDP/MTJ/Galileo Train Gap

Contents

Overview

Galileo Train define a list of must's and should's that each project must fulfill in order to join the train.

Initial Analysis

Below is an initial list of what was missing from current DSDP.MTJ.

Must

Any new third-party plug-ins that are common between projects must be consumed via 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).

Projects must have a written ramp down policy by M6+0, linked in the table above. (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 Platform 3.4 Endgame plan as a guideline. See also Galileo Final Daze.)

Projects must optimize their update site using pack200 to reduce bandwidth utilization and provide a better update experience for users. Additionally, they should do site digesting.

Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons.

Should

Should provide build RSS feeds as per the build workshop.

Should follow the User Interface Guidelines. The UI Checklist is a good place to start.

Requirements

Table coloring legend:

Finished

Not Finished

Need Special Attention

Must Do

Galileo Release "Must Do" Items

Category

Item

Description

Target Milestone

Master Bug

MTJ Bug

Status

Actions/Notes

Participation

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 bug 251715 and asking to have their project-specific bugs created as clones of each of those referenced in this table.

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.

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 Platform 3.4 Endgame plan as a guideline. See also Galileo Final Daze.)

Plug-in org.eclipse.mtj.ui is using Eclipse message bundles. We'll need to check other plug-ins that contribute to the UI.

APIs

As per the Jan 7 PC meeting [1], the requirement text was clarified as follows:

All deviations *must* be documented

Rectifications *should* be planned

Full new text below:

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? ;)

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.

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 bug 130598. With that, empty plugin.xml files in the presence of a manifest.mf file should not be included in a bundle.

Any new third-party plug-ins that are common between projects must be consumed via 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).

the build process was changed in order to consume antlr and asm plugins from orbit.

asm plugin content from mtj svn was removed. i added a README that describe how to checkout the content from orbit

antenna plugin was changed to remove the antlr classes from it.

mtj main feature was updated to include antlr plugin.

web site was updated to describe how to check out mtj code and also the orbit plugins

Optimization

Projects must optimize their own update site using 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).

The update site is optimized with pack200 and p2 metadata is being generated automatically on the build system

New & Noteworthy

Must have new & noteworthy for each milestone. Must be something readable and usable not just a static list of all the bugs, e.g. platform. Corollary: individual new & noteworthy should be linked in to the collective New & Noteworthy.

The "New & Noteworthy" was committed to SVN and will be available on the 1.0RC2 Release.

Deployment

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.

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.