Version 5 (modified by 6 years ago) ( diff ) | ,
---|
R1/beta2 Timeline
- Early May: Reminder to ML that R1/Beta2 work begins late August.
- 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
r1beta2
!- Branch
r1beta2
- Add
r1beta2
to ​buildbot and deploy - Buildbot and Buildmaster should be generating
r1beta2
RCs when forced. - Don't forget about HaikuPorts! We didn't branch Haikuports for
r1beta1
- Branch
- 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-r1b2 page (Draft = true)
- MOAR TESTING!
- 21 Sep - 28 Sep: one week of ham-fisting final images
- Rename your latest release candidate to
r1beta2
, move from haiku-r1beta2/XXX to haiku-release/r1beta2/ - 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-r1b2
- Update website
- Drop Draft on release-r1b2 page
- get-haiku _index should become release-r1b1
- release-r1b2 should become get-haiku _index
- Release when ready; some window to account for unexpected delays.
- Rename your latest release candidate to
Note:
See TracWiki
for help on using the wiki.