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.
TPTP 4.4 Plan
Back to main TPTP wiki page
Draft awaiting community approval
Based on the following snapshot taken from the Europa plan found here
Candidate milestone dates:
+0 | +1 | +2 | |
---|---|---|---|
M4 | Dec 15 | Dec 21 | Jan 4 |
M5 | Feb 9 | Feb 16 | Feb 23 |
M6 - API Freeze | Mar 23 | Mar 30 | Apr 6 |
M7 - RC0 | May 4 | May 11 | May 18 |
RCn... | |||
RCX | Jun 15 | ? | ? |
Europa | June 29 |
The TPTP 4.4 schedule will be as follows. This pattern is determined by creating test pass 2 candidates based on base (+1) milestone drivers that contain all dependencies. The base for test pass 1 and development drivers will be determined as the iteration progresses.
TPTP 4.4 release Schedule:
iteration | start | TP1 candidate | TP2 candidate | Release |
---|---|---|---|---|
I0 - M4 | Dec 15 | Jan 4 M4 | ||
I1 - M5 | Jan 8 | Feb 2 | Feb 16 | Feb 23 M5 |
I2 - M6 | Feb 26 | Mar 16 API Freeze | Mar 30 | Apr 6 M6 |
I3 - M7 | Apr 9 | Apr 27 | May 11 | May 18 RC0 |
I4 - RCs | May 21 | June 1 | June 8 | June 15 |
Europa | June 29 |
During a test pass no cvs code activity is expected until all testing is done and checked in. Commiters will instead help each other complete testing and if appropriate will work under the guidance of the sandbox wiki.
If a test pass completes early or if the candidate is ready early, the next phase in the schedule may begin early if approved by the PG/PMC.