R1/beta3 Timeline

• 26 Aug - 30 Aug: one week - last minute scramble.
  • Don't commit anything risky.
  • "Soft" strings freeze begins.
  • Testing starts ramping up.
• 30 Aug: branch r1beta3!
  • Branch r1beta3
  • Add r1beta3 to ​buildbot and deploy
  • Buildbot and Buildmaster should be generating r1beta3 RCs when forced.
  • Don't forget about HaikuPorts! We didn't branch Haikuports for r1beta1
• 30 Aug - 13 Sep: two weeks of xtreme testing
  • Generate test images as needed for testing.
  • All hands on deck testing of test images.
  • Unless any unfixable showstoppers are found, don't halt the release.
  • Do general polishing of release notes, website, etc. during this time.
• 13 Sep - 20 Sep: one week to "get the goods"
  • One final strings synchronization
  • Generate an image and name him "Release Candidate 1".
  • Begin work on draft ​https://www.haiku-os.org/get-haiku/release-r1b3 page (Draft = true)
  • MOAR TESTING!
• 21 Sep - 28 Sep: one week of ham-fisting final images
  • Rename your latest release candidate to r1beta3, move from haiku-r1beta3/XXX to haiku-release/r1beta3/
  • Double and triple check sha256 sums
  • Generate a torrent, begin seeding and get a few other people to seed.
  • Give a few hours for release to make it to the mirrors.
    • Force a sync to Wasabi
    • Sync up working mirrors and release-r1b3
  • Update website
    • Drop Draft on release-r1b3 page
    • get-haiku _index should become release-r1b1
    • release-r1b3 should become get-haiku_index
  • Release when ready; some window to account for unexpected delays.