Stage 2.0 Integration Plan
FRIDAY
- Inspections Done By Midnight (Everyone) - Merge Stage 1.1 code into Stage 2.0 (Mark)
SATURDAY
- Work on Defect Repair from Code Inspections (Everyone)
SUNDAY
- Complete Defect Repair from Code Inspections (Everyone)
INTEGRATION STARTS
Remember:
- Unit Test your code before committing!\par
Procedure:
Morning: Person1 Commit
Afternoon: Person2 Commit
Evening(7pm): Richard System Testing
Night(9pm): Fix Code (If necessary)
- Everyone will be allocated a time slot to commit and get your code to compile.
NO ONE else will be allowed to commit during another person's time allocation.
- Ideally two people are assigned to commit each day, one in the morning and one
in the afternoon. However you can negotiate with your "partner for the day"
what times work best for you to commit during that day. COMMITTING MUST be done
before 7pm so that Richard can System Test.
- Richard will System Test the newly commited code at 7pm (MTW) and let Paul and
the person assigned to the module know if code fails System Tests and needs to
be REWORKED via phone or email by 9pm that night.
- If code fails System Testing, then the person assigned to the module will have
from 9pm until 6am the next morning to get their code to pass the System
Tests.
TIME SLOTS
| WEEKDAY | PERSON | TIMEsLOT |
| MONDAY | Paul | 6am-12pm |
| Ian | 12pm-7pm | |
| TUESDAY | Steph | 6am-3pm |
| Tracy | 3pm-7pm | |
| WEDNESDAY | Richard | 6am-12pm |
| Mark | 12pm-7pm |
THURSDAY
- Post Integration Meeting
