JWT's automated build should be [https://bugs.eclipse.org/bugs/show_bug.cgi?id=405750 updated to use the new Maven Nexus repository] (instead of old Eclipse Maven repository which has been decomissionned).

+

+

Besides that, as previous one.

+

+

== Contents of JWT Contribution ==

+

+

As previous one.

+

+

== Build Schedule ==

+

+

*'''Offset:''' +3 (milestones 3 weeks after the platform milestones)

+

+

See the Google calendar of the Luna Schedule on the [[Luna/Simultaneous_Release_Plan]].

+

+

+

= Kepler =

= Kepler =

== ToDos ==

== ToDos ==

−

*State intent to contribute in portal before M4 (done) and check it in [http://projects.eclipse.org/releases/kepler Kepler project list] <br>

+

*State intent to contribute in portal before M4 (done) and check it in [http://projects.eclipse.org/releases/kepler Kepler project list]

*As for all releases, do [[JWT_DeveloperFAQ#Project_Management|Project Management]], [[JWT_DeveloperFAQ#Legal_Process|Legal_Process]] and [[JWT_DeveloperFAQ#1._Preparing| Release Preparation]]

*As for all releases, do [[JWT_DeveloperFAQ#Project_Management|Project Management]], [[JWT_DeveloperFAQ#Legal_Process|Legal_Process]] and [[JWT_DeveloperFAQ#1._Preparing| Release Preparation]]

Until M6+3

Continuous ramp-down: Builds almost every day, immediate inclusion of approved bugs. Contributors should always use the latest integration build to report bugs as fast as possible.

Integration of new feature: any new feature approved by the JWT team can be integrated into the builds. However, the feature must conform to the Galileo requirements before being included in build (mainly externalize string)

M6+3: Project Plan Freeze

At M6+3, we have to freeze the project plan. From here, we have a closed list of feature that we want to integrate into our Galileo release. Any other feature or enhancement request that will come after that date won't be integrated in JWTGalileo build.

EclipseCon: The M6+3 build is a few days before EclipseCon. This build will be used for tutorial and demo. Then all demo previewed for EclipseCon must be tested at M6+2 (a P1 bug will be opened at M6+1) on the integration build. Then, once all demos are working well, we build the milestone.

M7+3: Total Freeze

M7+3 will be the last build which will contain new feature until Galileo is released. After the date, no modification on UI, API or features will be accepted.

RC builds: The end-game

Only bug fixing, tests and tutorials for one month. Only P1, P2 and regression builds will be treated.

Issues and bug fixing

Let's use bugs priority to find out which bugs are to save first for milestones and release:

priority P1 means that the bug is to be fixed for next milestone

priority P2 means that the bug is to be fixed before RC1

Other priority are used for enhancements, new features and discussions

Thus, JWT is ready for Galileo when all P1 and P2 bugs are closed.

TODO list

Bugs

Galileo Build

Must Do

Galileo Release "Must Do" Items

Category

Item

Description

Deadline

Verification Method

JWT Bug

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 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.)

Projects should leverage only published APIs of dependencies. As a Release Review requirement, deviations 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? ;)

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.

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.

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 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).

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.

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.

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.

Each major project (as determined by participating PMCs) should have an About dialog icon with descriptive text (e.g. provider name = "Eclipse Modeling Project" and not simply Eclipse.org) and contribute to the welcome page.