==  R1/beta4 Timeline ==

A lot of these actions will be coordinated by the release coordinator and a sysadmin.

  * **31 October - 4 November**: one week - last minute scramble.
    * **Policy** Don't commit anything risky.
    * **Promotion team** begin investigating physical CD's or USB sticks?
    * **Policy** "Soft" strings freeze begins.
    * **Testing** Testing starts ramping up.
  * **1 November**: branch!
    * **Sysadmin** Branch {{{r1beta4}}}
    * **Policy** {{{r1beta4}}} branch bug fix only!
    * **Sysadmin** Add {{{r1beta4}}} to concourse
    * **Sysadmin** Concourse and Buildmaster should be generating {{{r1beta4}}} TCs when forced.
    * **Sysadmin** No haikuports branch, not enough infrastructure. We didn't branch Haikuports for prior releases
    * **Sysadmin** Generate an image and name it "Test Candidate 0"
    * **Sysadmin** Upgrade HaikuPorter Buildmaster to beta branch TC0 image
    * ICU upgrades?, build new webkit?
    * Opened logo contest for installer logo
  * **2 November - 16 November**: two weeks of **xtreme** testing
    * **Sysadmin** Generate additional "Test Candidate" images as needed for testing.
    * **Development** Work on fixing issues?
    * **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.
  * **16 November - 23 November**: one week to "get the goods"
    * One final strings synchronization
    * **Sysadmin** Generate an image and name it "Release Candidate 0".
    * Begin work on draft https://www.haiku-os.org/get-haiku/release page (Draft = true)
    * MOAR TESTING!
  * **23 November - 30 November**: one week of ham-fisting final images
    * **Promotion team** physical CD's or USB sticks?
    * **Sysadmin** Rename your latest release candidate to {{{r1beta4}}}, move from haiku-r1beta3/XXX to haiku-release/r1beta3/
    * **Sysadmin** Double and triple check sha256 sums
    * **Sysadmin** Generate a torrent, begin seeding and get a few other people to seed.
    * **Sysadmin** Give a few hours for release to make it to the mirrors.
      * **Sysadmin** Force a sync to Wasabi
        * DO not advertise final release images on Wasabi.. too much bandwidth.
      * **Sysadmin** Sync up working mirrors and release-r1b4
    * **Sysadmin** Push final images to IPFS repos and alert folks pinning to repin
      * **Sysadmin** Pin R1 / Beta 4 release folder CID on Pinata
    * **Sysadmin** Update website
    * Release when ready; some window to account for unexpected delays.