Difference between revisions of "DSDP/MTJ/Galileo Train Gap"
|Line 1:||Line 1:|
[[Galileo_Simultaneous_Release|Galileo Train]] define a list of must's and should's that each project must
[[Galileo_Simultaneous_Release|Galileo Train]] define a list of must's and should's that each project must in order to join the train. base on their requirements below is an initial list of what is missing from current DSDP.MTJ.
Revision as of 11:47, 22 September 2008
Galileo Train define a list of must's and should's that each project must fulfill in order to join the train. base on their requirements below is an initial list of what is missing from current DSDP.MTJ.
- 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 provide build RSS feeds as per the build workshop.
- Should follow the User Interface Guidelines. The UI Checklist is a good place to start.