| 3 | | The following timelines have been proposed for Beta 1 |
| 4 | | |
| 5 | | * two weeks - last minute scramble. Don't commit anything risky. |
| 6 | | * Branch R1B1 |
| 7 | | * Tag R1B1rc1 |
| 8 | | * 1 month - *Bug fixes only* |
| 9 | | * All hands on deck testing of release candidates. |
| 10 | | * Documentation work. |
| 11 | | * Weekly release candidates. Release Coordinator can adjust as needed. |
| 12 | | * Release is frozen |
| 13 | | * Point of no return, RC can no longer stop the release at this point. |
| 14 | | * 1 week Final testing and documentation of known bugs. |
| 15 | | * Final public release. |
| | 3 | * **18 Aug - 25 Aug**: one week - last minute scramble. |
| | 4 | * Don't commit anything risky. |
| | 5 | * "Soft" strings freeze begins. |
| | 6 | * Testing starts ramping up. |
| | 7 | * **25 Aug**: branch {{{r1beta1}}}! |
| | 8 | * Buildbot and Buildmaster should be generating beta1 RCs |
| | 9 | * Don't forget about HaikuPorts! |
| | 10 | * **25 Aug - 7 Sep**: |
| | 11 | * ''All hands on deck'' testing of release candidates. |
| | 12 | * Unless any unfixable showstoppers are found, don't halt the release. |
| | 13 | * Do general polishing of release notes, website, etc. during this time. |
| | 14 | * **7 Sep - 10 Sep** |
| | 15 | * Finalization of the "golden masters" (should just be images picked from the buildbot) |
| | 16 | * One final strings synchronization |
| | 17 | * **10 Sep - 18 Sep** |
| | 18 | * Release when ready; some window to account for unexpected delays. |
