Skip to main content
Jump to: navigation, search


Revision as of 12:04, 14 November 2008 by (Talk | contribs) (Must Do)

Must Do

Galileo Release "Must Do" Items
Category Item Description Target Milestone Master 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 Pending Eric will state the intent and modify wiki pages as necessary. Modify links to TmL pages.
Projects must have an project plan in XML format. M4 252790 Yes Completed in August. Eric 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 "". 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 Yes Fabio will be primary contact. Fabio will designate someone to 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 Yes Eric and Fabio 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 Pending Fabio will write first draft by M4 date for the team to review.
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 Yes For MOTODEV Studio contributions we may or may not need a CQ (investigations ongoing). Eric is trying to make contacts with Montavista regarding their contributions. Fabio submitted CQ on 11/12 to PMC for a vote.
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 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 [1]) M4 252795 Yes TmL already uses message bundles, so no action necessary.
Bundles Version Numbering Projects must use 4-part version numbers. M5 252796 Yes No action necessary
Leverage OSGi All plug-ins (bundles) must use the true bundle form. That is, provide a file, and not rely on the plugin.xml file being 'translated' into a file at initial startup. See bug 130598. With that, empty plugin.xml files in the presence of a file should not be included in a bundle. M5 252797 Pending Engineering team to review by M4 and verify if this is OK and fix if not. If a script is written, write by M6.
Execution Environment All plug-ins must correctly list their required JVM versions in the See the wiki page about selecting the correct JVM [2]. M5 252798 Pending Engineering team to review by M4.
Signing Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons. M4 252799 Pending Fabio to verify this is working. See "build scripts issues".
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 Manual (script?) 252800
Releng Builds Projects must have build process maturity: scripted, repeatable, and executable by others. M4 Manual 252801
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 Manual & Script 252803
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 Script 252804
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 Manual 252805
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 Manual 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. M6 Manual 252807
Localization The project participates in Babel, meaning it is registered and available for string translation, etc. M6 Script 252808
Must use ICU4J. M5 Manual 252809

Back to the top