...
| 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 :
| |||
| M1.1 | Staging repository setup | Oracle | Few hours | 1 day | At request of Lead | When JEP is Funded | Done | 2013/06/10 | |
| M1.2 | JIRA CPU and OS updates | Oracle | Few hours | 1 day | After M1.1 | July 2013 | Done | 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 | | ||
| M2 | Review and approve initial set of changes | ~4 weeks | ~6 weeks | After M1 | | 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 | | 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 | | The next set of patches (9-13) to get a working aix_ppc64 port | |
| M2.3 | Libraries porting effort | Oracle, SAP, IBM | ~4 weeks | ~6 weeks | After M1.3 | Early-Mid September | | ||
| M3 | Review and integrate architecture independent code, order of patches determined by SAP or IBM | ~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.1 | Low overhead tasks - 9 changesets | Oracle, SAP, IBM | ~6 weeks | ~7 weeks | After M2.2 | TBD | | Mostly straightforward | |
| M3.2 | Medium overhead tasks - 15 changesets | Oracle, SAP, IBM | ~12 weeks | ~15 weeks | After M2.2 | TBD | | Complication changes that require significant review and testing | |
| M3.3 | Large overhead task - 8 changesets | Oracle, SAP, IBM | ~12 weeks | ~15 weeks | After M2.2 | TBD | | Complicated changes that require significant review and testing | |
| M3.4 | Performance evaluation | Oracle, SAP, IBM | ~4 weeks | ~6 weeks | After M3.3 | TBD | | All performance criteria resolved | |
| M4 | Stabilization/post integration bug fixing | Oracle, SAP, IBM | ~4 weeks | ~8 weeks | After all milestones | After all milestones | | 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 | | Verification of all integrated changes, including a functional satisfaction report by SAP and IBM |
...
Overview
Content Tools
ThemeBuilder