Page History

...

Confidence level maps to the following:

 = Low effort or high confidence in meeting the expected effort schedule

 = Medium effort or medium confidence in meeting the expected effort schedule

= High effort or low confidence in meeting the expected effort schedule

Milestone	Task	Who	Effort (expected)	Effort (pessimistic)	Dependency	Target Date	Confidence Level (, , )	Completed	Comments
M1	Setup		~1 day (M1.1 + 1.2 + 1.3)	~1 week (M1.1 + 1.2 + 1.3)	When JEP is Funded				Funded: 2013/06/10 : notification
M1.1	Staging repository setup	Oracle	Few hours	1 day	At request of Lead	When JEP is Funded		Done 2013/06/10	:  http://hg.openjdk.java.net/ppc-aix-port/stage
M1.2	JIRA CPU and OS updates	Oracle	Few hours	1 day	After M1.1	July 2013		2013/07/12	OS value "aix" added.  New CPU field unnecessary. The following fields should be updated.  OS would have a new field 'aix' with optionally adding version post fix such as 'aix_7.1' or 'aix_6'.  The CPU would have a new field 'ppc64'.
M1.3	Hudson instance on staging server	Oracle	Few hours	1 day	After M1.1	July 2013		2013/08/01
M2	Review and approve initial set of changes		~4 weeks	~6 weeks	After M1			2013/11/28	The work can happen mostly in parallel, with M2.1 and M2.2 taking roughly the same time to complete as M2.3.
M2.1	Review changes for a working linux_ppc64 hotspot port	Oracle, SAP, IBM	~2 weeks	~3 weeks	After M1.3	Mid-Late August		2013/08/20	The initial 8 changes (1-8) that get a working linux_ppc64 port
M2.2	Review changes for a working aix_ppc64 hotspot port	Oracle, SAP, IBM	~2 weeks	~3 weeks	After M1.3	Mid-Late August		2013/09/06	The next set of patches (9-13) to get a working aix_ppc64 port
M2.3	Libraries Basic libraries porting effort	Oracle, SAP, IBM	~4 ~2 weeks	~6 ~4 weeks	After M1.3	Early-Mid September		October		2013/11/28	Enabling the build and basic functionality of the complete JDK on Linux and AIX.
M3	Review and integrate architecture independent code, order of patches determined by SAP or IBMPPC64/C2 and advanced HotSot changes and the remaining AIX class library changes.		~34 weeks (M3.1 + 3.2 + 3.3 + 3.4)	~43 weeks (M3.1 + 3.2 + 3.3 + 3.4)	After M2				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.1Low overhead tasks - 9 changesets	HotSpot changes for the PPC64 C2 Port	Oracle, SAP, IBM	~6 weeks	~7 weeks	After M2.2	December	TBD			2013/12/13	Basic changes for a running C2 Port on PPC64 (~10 changes).Mostly straightforward
M3.2Medium overhead tasks - 15 changesets	Remaining HotSpot changes for PPC64.	Oracle, SAP, IBM	~12 weeks	~15 weeks	After M2.2	TBD		February 2014		2014/01/22	Additional C2 and runtime/GC changes which fix remaining problems and improve the performance.Complication changes that require significant review and testing
M3.3Large overhead task - 8 changesets	Complete and stabilize class library port.	Oracle, SAP, IBM	~12 weeks	~15 weeks	After M2.2	TBD		February 2014		2014/01/24	Add class library functionality which is missing on AIX and improve the implementation.Complicated changes that require significant review and testing
M3.4	Performance evaluation	Oracle, SAP, IBM	~4 weeks	~6 weeks	After M3.3	TBD	March 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		2014/03/27	Verification of all integrated changes, including a functional satisfaction report by SAP and IBM

...