Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
JWT Ramp-Down-Policy
Revision as of 05:47, 3 December 2008 by Mickael.istria.openwide.fr (Talk | contribs) (→Build Schedule)
Galileo
Build Schedule
- Offset: +3 (milestones 3 weeks after the platform milestones)
| 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 |
- 0.6 JWT for Vendors (EMF aspects, completeness and consistency of extensions, first transformations) - aiming at the end 2008
- 0.7 JWT for SOA (more transformations, runtime APIs in WAM, service search UI, service applications model) - Start of 2009
- 1.0 JWT for Users (With comprehensive testing and documentation,and one or more advised target workflow engine working as well) - aiming at Galileo timeline (June 2009)
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.