| 1 | == R1/beta3 Timeline == |
| 2 | |
| 3 | * **26 Aug - 30 Aug**: one week - last minute scramble. |
| 4 | * Don't commit anything risky. |
| 5 | * "Soft" strings freeze begins. |
| 6 | * Testing starts ramping up. |
| 7 | * **30 Aug**: branch {{{r1beta3}}}! |
| 8 | * Branch {{{r1beta3}}} |
| 9 | * Add {{{r1beta3}}} to [https://github.com/haiku/infrastructure/blob/master/data/buildbot/master.cfg#L329 buildbot] and deploy |
| 10 | * Buildbot and Buildmaster should be generating {{{r1beta3}}} RCs when forced. |
| 11 | * Don't forget about HaikuPorts! We didn't branch Haikuports for {{{r1beta1}}} |
| 12 | * **30 Aug - 13 Sep**: two weeks of **xtreme** testing |
| 13 | * Generate test images as needed for testing. |
| 14 | * ''All hands on deck'' testing of test images. |
| 15 | * Unless any unfixable showstoppers are found, don't halt the release. |
| 16 | * Do general polishing of release notes, website, etc. during this time. |
| 17 | * **13 Sep - 20 Sep**: one week to "get the goods" |
| 18 | * One final strings synchronization |
| 19 | * Generate an image and name him "Release Candidate 1". |
| 20 | * Begin work on draft https://www.haiku-os.org/get-haiku/release-r1b3 page (Draft = true) |
| 21 | * MOAR TESTING! |
| 22 | * **21 Sep - 28 Sep**: one week of ham-fisting final images |
| 23 | * Rename your latest release candidate to {{{r1beta3}}}, move from haiku-r1beta3/XXX to haiku-release/r1beta3/ |
| 24 | * Double and triple check sha256 sums |
| 25 | * Generate a torrent, begin seeding and get a few other people to seed. |
| 26 | * Give a few hours for release to make it to the mirrors. |
| 27 | * Force a sync to Wasabi |
| 28 | * Sync up working mirrors and release-r1b3 |
| 29 | * Update website |
| 30 | * Drop Draft on release-r1b3 page |
| 31 | * get-haiku _index should become release-r1b1 |
| 32 | * release-r1b3 should become get-haiku_index |
| 33 | * Release when ready; some window to account for unexpected delays. |