Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "JWT Ramp-Down-Policy"

(→‎Galileo)
(→‎Galileo)
Line 55: Line 55:
  
 
Thus, JWT is ready for Galileo when all P1 and P2 bugs are closed.
 
Thus, JWT is ready for Galileo when all P1 and P2 bugs are closed.
 +
 +
== TODO list ==
 +
 +
TODO replace milestones by deadlines and master bugs by JWT bugs
 +
 +
==== Must Do ====
 +
{| border="1" cellpadding="3" cellspacing="1"
 +
|+ '''Galileo Release "Must Do" Items'''
 +
! style="background:#efefef;" | Category
 +
! style="background:#efefef;" | Item
 +
! style="background:#efefef;" | Description
 +
! style="background:#efefef;" | Deadline
 +
! style="background:#efefef;" | Verification Method
 +
! style="background:#efefef;" | JWT Bug
 +
|-
 +
| rowspan="6" | Participation
 +
| rowspan="2" | 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 [https://bugs.eclipse.org/bugs/show_bug.cgi?id=251715 251715] and asking to have their project-specific bugs created as clones of each of those referenced in this table.
 +
| align="center" | M4
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=251715 251715]
 +
|-
 +
| Projects must have an project plan in [http://wiki.eclipse.org/Development_Resources/Project_Plan XML format].
 +
| align="center" | M4
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252790 252790]
 +
|-
 +
| 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.
 +
| align="center" | M4
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252789 252789]
 +
|-
 +
| Attendance
 +
| Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved.
 +
| align="center" | M4
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252791 252791]
 +
|-
 +
| 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 [http://www.eclipse.org/eclipse/development/freeze_plan_3.4.php Platform 3.4 Endgame plan] as a guideline. See also [[Galileo/Final Daze|Galileo Final Daze]].)
 +
| align="center" | M5
 +
| align="center" | Script
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252792 252792]
 +
|-
 +
| 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}}.
 +
| align="center" | CQs submitted by M5, completed by RC3
 +
| align="center" | Manual (Legal)
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252793 252793]
 +
|-
 +
| rowspan="2" | 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?''' ;)
 +
| align="center" | M6
 +
| align="center" | [http://www.eclipse.org/pde/pde-api-tools/ PDE API Tools]
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252794 252794]
 +
|-
 +
| Message Bundles
 +
| Projects must use Eclipse message bundles unless there are technical reasons not to. (see [[Message Bundle Conversion Tool]] and [http://www.eclipse.org/eclipse/platform-core/documents/3.1/message_bundles.html])
 +
| align="center" | M4
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252795 252795]
 +
|-
 +
| rowspan="5" | Bundles
 +
| Version Numbering
 +
| Projects must use 4-part [[Version Numbering|version numbers.]]
 +
| align="center" | M5
 +
| align="center" | Manual (script?)
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252796 252796]
 +
|-
 +
| 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 [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130598 bug 130598]. With that, empty plugin.xml files in the presence of a manifest.mf file should not be included in a bundle.
 +
| align="center" | M5
 +
| align="center" | Manual (script?)
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252797 252797]
 +
|-
 +
| 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 [http://wiki.eclipse.org/index.php/EMF_2.3_JVM_Requirements#Runtime_.2F_Compilation_Compatibility].
 +
| align="center" | M5
 +
| align="center" | Manual (script?)
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252798 252798]
 +
|-
 +
| Signing
 +
| Projects must use [[Modeling_Project_Releng/Building/Signing_And_Packing|signed plugins]] using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons.
 +
| align="center" | M4
 +
| align="center" | Script
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252799 252799]
 +
|-
 +
| 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.
 +
| align="center" | M4
 +
| align="center" | Manual (script?)
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252800 252800]
 +
|-
 +
| rowspan="4" | Releng
 +
| Builds
 +
| Projects must have build process maturity: scripted, repeatable, and executable by others.
 +
| align="center" | M4
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252801 252801]
 +
|-
 +
| Orbit
 +
| Any new third-party plug-ins that are common between projects must be consumed via [http://www.eclipse.org/orbit/ 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).
 +
| align="center" | M4
 +
| align="center" | Manual & Script
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252803 252803]
 +
|-
 +
| Optimization
 +
| Projects must [[Update_Site_Optimization|optimize]] their own update site using [[Pack200|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).
 +
| align="center" | M4
 +
| align="center" | Script
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252804 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. [http://download.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/whatsnew3.4/eclipse-news.html platform]. Corollary: individual new & noteworthy should be linked in to the collective New & Noteworthy.
 +
| align="center" | RC
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252805 252805]
 +
|-
 +
| rowspan="5" | 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.
 +
| align="center" | RC
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252806 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.
 +
| align="center" | M6
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252807 252807]
 +
|-
 +
| rowspan="2" |  Localization
 +
| The project participates in Babel, meaning it is registered and available for string translation, etc.
 +
| align="center" | M6
 +
| align="center" | Script
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252808 252808]
 +
|-
 +
| Must use [[ICU4J | ICU4J]].
 +
| align="center" | M5
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252809 252809]
 +
|-
 +
| Branding
 +
| Each major project (as determined by participating PMCs) should have an About dialog icon with [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252813198941 descriptive text] (e.g. provider name = "Eclipse Modeling Project" and not simply Eclipse.org) and contribute to the welcome page.
 +
| align="center" | RC
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252813 252813]
 +
|}
 +
 +
==== Should Do ====
 +
{| border="1" cellpadding="3" cellspacing="1"
 +
|+ '''Galileo Release "Should Do" Items'''
 +
! style="background:#efefef;" | Item
 +
! style="background:#efefef;" | Description
 +
! style="background:#efefef;" | Target Milestone
 +
! style="background:#efefef;" | Verification Method
 +
! style="background:#efefef;" | Master Bug
 +
|-
 +
| 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]] [[UIBPWG UI Walkthrough | UI walkthrough]].
 +
| align="center" | M5
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252810]
 +
|-
 +
| Accessibility
 +
| Should design and test for accessibility.
 +
| align="center" | M4
 +
| align="center" | [http://www.eclipse.org/actf/ ACTF]
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252811]
 +
|-
 +
| Performance
 +
| Projects should devote at least one milestone to performance and scalability improvements.
 +
| align="center" | M7
 +
| align="center" | [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.test.performance/doc/Performance%20Tests%20HowTo.html?view=co]
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252812]
 +
|-
 +
| rowspan="3" | Localization
 +
| The project should use the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339 Babel Pseudo Translation Test] to verify their translatablity.
 +
| align="center" | M6
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252814]
 +
|-
 +
| Should freeze the UI sufficiently early to allow the Babel project time to translate strings.
 +
| align="center" | M6
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252815]
 +
|-
 +
| Should design and test for enabling all languages including bidi, unicode characters, etc.
 +
| align="center" | M7
 +
| align="center" | Manual
 +
| align="center" | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=252815]
 +
|}

Revision as of 12:43, 4 December 2008

Galileo

Build Schedule

  • Offset: +3 (milestones 3 weeks after the platform milestones)
JWT in Galileo build Schedule
Date Name JWT Release
December 2008 0.6 JWT for Vendors
5th january 2008 Galileo M4 + 3
10th february 2008 Galileo M5 + 3
end of february 2009 0.7 JWT for SOA
19th march 2008 Galileo M6 + 3
april or may 2008 1.0 JWT for Users
6th may 2008 Galileo M7 + 3
Every wednesday from 20th may Galileo RC n + 3


See also JWT Roadmap

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

TODO replace milestones by deadlines and master bugs by JWT bugs

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. M4 Manual 251715
Projects must have an project plan in XML format. M4 Manual 252790
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 Manual 252789
Attendance Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved. M4 Manual 252791
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 Script 252792
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 Manual (Legal) 252793
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 PDE API Tools 252794
Message Bundles Projects must use Eclipse message bundles unless there are technical reasons not to. (see Message Bundle Conversion Tool and [1]) M4 Manual 252795
Bundles Version Numbering Projects must use 4-part version numbers. M5 Manual (script?) 252796
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 Manual (script?) 252797
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 [2]. M5 Manual (script?) 252798
Signing Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons. M4 Script 252799
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
Branding 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. RC Manual 252813

Should Do

Galileo Release "Should Do" Items
Item Description Target Milestone Verification Method Master Bug
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 Manual [3]
Accessibility Should design and test for accessibility. M4 ACTF [4]
Performance Projects should devote at least one milestone to performance and scalability improvements. M7 [5] [6]
Localization The project should use the Babel Pseudo Translation Test to verify their translatablity. M6 Manual [7]
Should freeze the UI sufficiently early to allow the Babel project time to translate strings. M6 Manual [8]
Should design and test for enabling all languages including bidi, unicode characters, etc. M7 Manual [9]
Retrieved from "https://wiki.eclipse.org/index.php?title=JWT_Ramp-Down-Policy&oldid=131118"

Back to the top