Skip to main content
Jump to: navigation, search

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

m (Helios release)
Line 17: Line 17:
* [[Building|Building Information]]
* [[Building|Building Information]]
* [ Planning Council Calendar]
* [ Planning Council Calendar]
=== JWT ===
=== JWT ===
Line 27: Line 26:
* [[JWT_Automatic_Build|JWT Automatic Build]]
* [[JWT_Automatic_Build|JWT Automatic Build]]
* [ Test Report]
* [ Test Report]
* [ JWT in Hudson]
==== Update sites ====
==== Update sites ====

Revision as of 10:15, 22 September 2009




Helios release



Galileo release


Update sites


Content of the JWT feature for Galileo

  • JWT Workflow Editor org.eclipse.jwt.we OK
  • JWT Workflow Editor - Aspect extensions OK
    • org.eclipse.jwt.we.conf
    • org.eclipse.jwt.we.conf.edit
    • org.eclipse.jwt.we.conf,model
    • org.eclipse.jwt.we.conf.we
  • JWT Workflow Editor - UML Activity Diagram view org.eclipse.jwt.we.plugins.viewuml OK
  • JWT Workflow Editor - EPC view org.eclipse.jwt.we.plugins.view.epc OK
  • JWT Workflow Editor - HTML documentation org.eclipse.jwt.we.plugins.doc OK
  • JWT Workflow Editor - new View Editor (will be uploaded to IPZilla today) org.eclipse.jwt.we.we_view_editor OK
  • JWT Transformation - base for transformations org.eclipse.jwt.transformations.baseTransformation OK
  • JWT Transformation - XSL Tools OK
  • JWT Transformation - JWT to XPDL transformation org.eclipse.jwt.transformations.xpdl OK
  • JWT Transformation - JWT to BPMN transformation org.eclipse.jwt.transformations.bpmn OK
  • JWT Transformation - BPMN to JWT transformation org.eclipse.jwt.transformations.bpmn OK
  • JWT Transformation - JWT to STP-IM transformation TODO Need code
  • JWT Feature - Branding org.eclipse.jwt OK
  • JWT Workflow Editor - Helpers for Application and File OK
    • org.eclipse.jwt.we.helpers.application
    • org.eclipse.jwt.we.helpers.files
  • And dependencies: Xalan, Xerces...

Build Schedule

  • Offset: +3 (milestones 3 weeks after the platform milestones)
JWT in Galileo build Schedule
Date Name JWT Release Ramp-Down
5th january 2008 Galileo M4 + 3
10th february 2008 Galileo M5 + 3
end of february 2009 0.6 JWT for Vendors
19th march 2008 Galileo M6 + 3 EclipseCon, Project Plan freeze
april or may 2008 0.7 JWT for SOA
6th may 2008 Galileo M7 + 3 API Freeze, Feature freeze, UI Freeze
Every wednesday from 20th may Galileo RC n + 3 Bug fixing only
24th june 2009 Galileo GA
End of summer 2009 1.0 JWT for users JWT Graduation release

See also JWT Roadmap

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 to fix for next milesoone:

Galileo Build

See 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. 5th january 2008 Manual 257551
Projects must have an project plan in XML format. 5th january 2008 Manual 257553
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. 5th january 2008 Manual 257555
Attendance Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved. 5th january 2008 Manual 257558
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.) 10th february 2008 Script 257559
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) 257560
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? ;) 19th march 2008 PDE API Tools 257561
Message Bundles Projects must use Eclipse message bundles unless there are technical reasons not to. (see Message Bundle Conversion Tool and [1]) 5th january 2008 Manual 257562
Bundles Version Numbering Projects must use 4-part version numbers. 10th february 2008 Manual (script?) 257563
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. 10th february 2008 Manual (script?) 257564
Execution Environment All plug-ins must correctly list their required JVM versions in the See the wiki page about selecting the correct JVM [2]. 10th february 2008 Manual (script?) 257565
Signing Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons. 5th january 2008 Script 257566
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. 5th january 2008 Manual (script?) 257567
Releng Builds Projects must have build process maturity: scripted, repeatable, and executable by others. 5th january 2008 Manual 257568
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). 5th january 2008 Manual & Script 257569
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). 5th january 2008 Script 257570
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 257571
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 257573
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. 19th march 2008 Manual 257576
Localization The project participates in Babel, meaning it is registered and available for string translation, etc. 19th march 2008 Script 257578
Must use ICU4J. 10th february 2008 Manual 257579
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 and contribute to the welcome page. RC Manual 257580

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. 10th february 2008 Manual [3]
Accessibility Should design and test for accessibility. 5th january 2008 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. 19th march 2008 Manual [7]
Should freeze the UI sufficiently early to allow the Babel project time to translate strings. 19th march 2008 Manual [8]
Should design and test for enabling all languages including bidi, unicode characters, etc. M7 Manual [9]

Planning Council Conference Call

See Planning Council#Call and Meeting Schedule. And a tool for converting UTC time (always 15:00 UTC for conf calls) to your timezone =>

See also

JWT Automatic Build to know how to build JWT automatically.

Back to the top