Project planning: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 72: | Line 72: | ||
*M1 release XUL extensions | *M1 release XUL extensions | ||
*System code skeleton created | *System code skeleton created | ||
*Initial integration tests for M1 | *Initial integration tests for M1 release | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
*[http://www.salesforce.com/dreamforce/ Dreamforce] | *[http://www.salesforce.com/dreamforce/ Dreamforce] | ||
Line 84: | Line 80: | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
*Integration tests needed for | *Module code for M1 complete | ||
*Integration tests needed for M1 release pass | |||
*Packaging | |||
*M1 release | |||
|} | |} | ||
<br> | <br> | ||
Line 100: | Line 99: | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
*Integration tests needed for version M2 release | |||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
|width="12.5%" valign="top"| | |width="12.5%" valign="top"| | ||
*Module code for M2 | |||
*Integration tests needed for the M2 release pass | |||
*Packaging | |||
*M2 release | |||
|} | |} |
Revision as of 18:00, 16 September 2007
Schedule
The first release of Thunderforce is planned to occur around mid-August of this year. The details of the plan will work backwards from that release date.
The following table depicts the current schedule for Thunderforce. Weeks begin on Mondays in this schedule. Note that week 18 is the week beginning on April 30, 2007. Items in the table cells indicate when those activities should be completed by, which can be by the end of the week indicated.
Please note that, as with any open-source software project, this schedule does not constitute any promise of delivery or adherence.
Week 18 | Week 19 | Week 20 | Week 21 | Week 22 | Week 23 | Week 24 | Week 25 |
---|---|---|---|---|---|---|---|
|
|
|
|
|
Week 26 | Week 27 | Week 28 | Week 29 | Week 30 | Week 31 | Week 32 | Week 33 |
---|---|---|---|---|---|---|---|
|
|
|
Week 34 | Week 35 | Week 36 | Week 37 | Week 38 | Week 39 | Week 40 | Week 41 |
---|---|---|---|---|---|---|---|
|
|
|
Week 42 | Week 43 | Week 44 | Week 45 | Week 46 | Week 47 | Week 48 | Week 49 |
---|---|---|---|---|---|---|---|
|
|