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.
Difference between revisions of "JWT Ramp-Down-Policy"
(→Build Schedule) |
(→Build Schedule) |
||
| Line 44: | Line 44: | ||
|} | |} | ||
| − | + | ||
| − | + | See also [[Java Workflow Tooling Project | JWT Roadmap]] | |
| − | + | ||
== Issues and bug fixing == | == Issues and bug fixing == | ||
Revision as of 06:51, 3 December 2008
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 |
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.