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.
JWT Ramp-Down-Poliy
Galileo
Build Schedule
- Offset: +3 (milestones 3 weeks after the platform milestones)
| Date | Name |
|---|---|
| 5th january 2008 | Galileo M4 + 3 |
| 10th february 2008 | Galileo M5 + 3 |
| 19th march 2008 | Galileo M6 + 3 |
| 6th may 2008 | Galileo M7 + 3 |
| Every wednesday from 20th may | Galileo RC n + 3 |
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.