None of the sub milestones are dependent on each other, they can happen in any order as the PPC/AIX project members see fit. While the milestones are not dependent on each other, there are resource constraints that will not allow them to happen in parallel.

M3.1

HotSpot changes for the PPC64 C2 Port

Oracle, SAP, IBM

~6 weeks

~7 weeks

After M2.2

December

2013/12/13

Basic changes for a running C2 Port on PPC64 (~10 changes).

M3.2

Remaining HotSpot changes for PPC64.

Oracle, SAP, IBM

~12 weeks

~15 weeks

After M2.2

February 2014

2014/01/22

Additional C2 and runtime/GC changes which fix remaining problems and improve the performance.

M3.3

Complete and stabilize class library port.

Oracle, SAP, IBM

~12 weeks

~15 weeks

After M2.2

February 2014

2014/01/24

Add class library functionality which is missing on AIX and improve the implementation.

M3.4

Performance evaluation

Oracle, SAP, IBM

~4 weeks

~6 weeks

After M3.3

TBDMarch 2014

All performance criteria resolved

M4

Stabilization/post integration bug fixing

Oracle, SAP, IBM

~4 weeks

~8 weeks

After all milestones

After all milestones

March 2014

Extended testing on the completed integration will testing and performance regressions resolved

M5

Final integration

Oracle, SAP, IBM

< 1 week

1 week

After stabilization period

After stabilization period

March 2014

Verification of all integrated changes, including a functional satisfaction report by SAP and IBM