Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
DSDP/TML/EclipseGalileoPlanning
| Tools for Mobile Linux |
| TmL Web Site |
| Project Summary |
| Mailing List |
| TmL Wiki |
| Regular Phone Meetings |
| Galileo Planning |
TmL- Tools for Mobile Linux - Eclipse Galileo Planning
Overview
This page reflects the TmL Project current status reflected against the requirements of the Eclipse Galileo Simultaneous Release. http://wiki.eclipse.org/Galileo_Simultaneous_Release
Milestone Dates
TmL is currently planning to release at offset + 0 as we have no dependencies on other projects. We are investigating TCF, which is in DSDP-TM, which is on offset + 2. If we adopt TCF, we may end up at offset + 2.
| Milestone | Date |
|---|---|
| M4 | 12/12/2008 |
| M5 | 1/30/2009 |
| M6 | 3/13/2009 |
| M7 | 5/1/2009 |
| RC1 | 5/15/2009 |
| RC2 | 5/22/2009 |
| RC3 | 5/29/2009 |
| RC4 | 6/5/2009 |
Requirements
Must Do
| Category | Item | Description | Target Milestone | Master Bug | TmL Bug | TmL 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 the table/list above, by signing off each milestone/RC on the Galileo/Signoffs page, and by contributing appropriate build contribution. | M4 | 251715 | 257283 | Yes | Eric Cloninger has stated the intent and modify wiki pages as necessary. Bug 257283 through 257310 as a result. |
| Projects must have an project plan in XML format. | M4 | 252790 | 257285 | Yes | Completed in August 2008. Eric Cloninger made changes on 11/12 reflecting current status. | ||
| 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. | M4 | 252789 | 257284 | Yes | Fabio Fantato will be primary contact and Daniel Franco will be secondary contact. (mailing list - ok, bug watch - ok, information - ok) | |
| Attendance | Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved. | M4 | 252791 | 257286 | Yes | Eric Cloninger and Fabio Fantato are on all necessary mailing lists. Eric attends and participates in monthly DSDP PMC calls. The TmL team has bi-weekly scheduled open meetings. | |
| 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 Platform 3.4 Endgame plan as a guideline. See also Galileo Final Daze.) | M5 | 252792 | 257287 | Yes | See [1] | |
| 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. | CQs submitted by M5, completed by RC3 | 252793 | 257288 | Yes | apache.oro and apache.common.net orbit | |
| Development | APIs | 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? ;) | M6 | 252794 | 257289 | Yes | We use only published APIs currently. We will continue to track this aspect as the milestones progress. No other action necessary. |
| Message Bundles | Projects must use Eclipse message bundles unless there are technical reasons not to. (see Message Bundle Conversion Tool and [2]) | M4 | 252795 | 257290 | Yes | TmL already uses message bundles, so no action necessary. | |
| Bundles | Version Numbering | Projects must use 4-part version numbers. | M5 | 252796 | 257291 | Yes | No action necessary |
| 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 bug 130598. With that, empty plugin.xml files in the presence of a manifest.mf file should not be included in a bundle. | M5 | 252797 | 257292 | Yes | Reviewed.No action is required | |
| 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 [3]. | M5 | 252798 | 257293 | Yes | Reviewed.No action is required | |
| Signing | Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons. | M4 | 252799 | 257294 | Yes | Reviewed. No action is required for this release. In the future need to be reviewd to use the common build infrastructure | |
| 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. | M4 | 252800 | 257295 | Yes | All TmL plugins satisfy this requirement. | |
| Releng | Builds | Projects must have build process maturity: scripted, repeatable, and executable by others. | M4 | 252801 | 257296 | Yes | Reviewed. No action is required |
| Orbit | 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). | M4 | 252803 | 257297 | Yes | TmL 0.1 (current release) has no dependency. TmL 0.3 (Galileo train) may have a dependency on Orbit for JDOM.
. There is a IP issue related to this bug | |
| 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). | M4 | 252804 | 257298 | Yes | Reviewed. No action is required | |
| 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. | RC | 252805 | 257299 | Pending | There are a first draft on the wiki page. This page should be shared with the community to be reviewed for whole community. | |
| 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. | RC | 252806 | 257300 | Yes | TmL does not affect other projects. |
| 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. | M6 | 252807 | 257301 | Yes | Reviewed.No action is required | |
| Localization | The project participates in Babel, meaning it is registered and available for string translation, etc. | M6 | 252808 | 257302 | Yes | subscribed into Babel project | |
| Must use ICU4J. | M5 | 252809 | 257303 | Yes | Reviewed. No action is required | ||
| Branding | Each major project (the top-level projects except for the Tools and Technology projects where it is the sub-projects) should have an About dialog icon and contribute to the welcome page. | RC | [4] | 257307 | Yes | The DSDP projects will all use one top-level icon, to be delivered by Doug Gaff. See the thread branding in the mailing list. |
Should Do
| Item | Description | Target Milestone | Master Bug | TmL Bug | TmL Status | Actions/Notes |
|---|---|---|---|---|---|---|
| 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 UI walkthrough. | M5 | [5] | 257304 | Yes | Eric and Fabio reviewed before M4 |
| Accessibility | Should design and test for accessibility. | M4 | [6] | 257305 | No | Eric and Fabio reviewed |
| Performance | Projects should devote at least one milestone to performance and scalability improvements. | M7 | [7] | 257306 | Yes | Some bugs during the M7 phase already addresses the performance issues. |
| Localization | The project should use the Babel Pseudo Translation Test to verify their translatablity. | M6 | [8] | 257308 | Yes | |
| Should freeze the UI sufficiently early to allow the Babel project time to translate strings. | M6 | [9] | 257309 | Yes | UI has been frozen in M6 | |
| Should design and test for enabling all languages including bidi, unicode characters, etc. | M7 | [10] | 257310 | No | There are few UI available to be tested. Does not make sense to cover this for the current release |