Haiku/haiku
Haiku/haiku
1
0
Fork 0
mirror of https://review.haiku-os.org/haiku synced 2025-01-19 04:58:51 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
9105063938
haiku/docs/develop/release/index.rst

54 lines
2.3 KiB
ReStructuredText
Raw Normal View History

docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
Release engineering
===================
docs/develop/release: add the info from the ReleaseCookbook Trac wiki page The corresponding Trac wiki page can be deleted once this is merged. Some of this information is a little out of date, help is welcome on updating it. Change-Id: I9157b140bcb5de3fed3c95d994745b5a1cbee1f6 Reviewed-on: https://review.haiku-os.org/c/haiku/+/5477 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
2022-07-15 22:11:57 +02:00
To forge a successful stable release of the Haiku operating system, several important tasks must be
accomplished. These steps are time tested as a best roadmap to draft a successful release of Haiku.
.. toctree::
docs/develop: Rename release "milestones" page to "cookbook". This more accurately reflects what it contains, as well as mirrors what it used to be called when it was on Trac.
2024-08-20 19:13:24 +02:00
cookbook
docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
Important first steps
---------------------
docs/develop/release: add the info from the ReleaseCookbook Trac wiki page The corresponding Trac wiki page can be deleted once this is merged. Some of this information is a little out of date, help is welcome on updating it. Change-Id: I9157b140bcb5de3fed3c95d994745b5a1cbee1f6 Reviewed-on: https://review.haiku-os.org/c/haiku/+/5477 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
2022-07-15 22:11:57 +02:00
* Review blockers for the next release in `Trac <https://dev.haiku-os.org>`_
* Active members of the `contributors group <https://review.haiku-os.org/admin/groups/23fa29f291e2dd5d41452202147d038f020fc8db,members>`_ should reach concensus on the need for a stable release
* We try to have a release every year, but blocker tickets can prevent this from happening
* It's difficult to commit to strictly time-based releases because the available time of unpaid developers is unpredictable
docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
* Community nomination of a Release Coordinator
* Should be someone from the contributors group
* Should have visibility of most aspects of Haiku
* Should have good coordination and communication skills
docs/develop/release: add the info from the ReleaseCookbook Trac wiki page The corresponding Trac wiki page can be deleted once this is merged. Some of this information is a little out of date, help is welcome on updating it. Change-Id: I9157b140bcb5de3fed3c95d994745b5a1cbee1f6 Reviewed-on: https://review.haiku-os.org/c/haiku/+/5477 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
2022-07-15 22:11:57 +02:00
* Generally occurs via the haiku-development mailing list
docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
* Timeline proposals are proposed via the haiku-development mailing list
docs/develop/release: add the info from the ReleaseCookbook Trac wiki page The corresponding Trac wiki page can be deleted once this is merged. Some of this information is a little out of date, help is welcome on updating it. Change-Id: I9157b140bcb5de3fed3c95d994745b5a1cbee1f6 Reviewed-on: https://review.haiku-os.org/c/haiku/+/5477 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
2022-07-15 22:11:57 +02:00
General Rules
-------------
* Don't rush the release. Better delay it a bit and take the time to make sure everything is ok.
* Make sure the final image is really well tested.
* Start planning early. Getting the release ready takes time. Waiting until a new release is urgent is a bad idea.
* There will be another release. Maybe some big changes are too risky to integrate now, and should wait until the next release.
docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
Forming a timeline
------------------
docs/develop/release: add the info from the ReleaseCookbook Trac wiki page The corresponding Trac wiki page can be deleted once this is merged. Some of this information is a little out of date, help is welcome on updating it. Change-Id: I9157b140bcb5de3fed3c95d994745b5a1cbee1f6 Reviewed-on: https://review.haiku-os.org/c/haiku/+/5477 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
2022-07-15 22:11:57 +02:00
An important aspect of drafting a release is forming a timeline. The Release Coordinator's role is
to drive Haiku towards this release date.
docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
* Final date for enhancements in (RELEASE)
* Branch buildtools for (RELEASE)
* Branch haiku for (RELEASE)
* Setup CI/CD pipelines for (RELEASE)
* Generate first test candidates (TC0, TC1, etc), encourage extreme testing.
docs/develop: Rename release "milestones" page to "cookbook". This more accurately reflects what it contains, as well as mirrors what it used to be called when it was on Trac.
2024-08-20 19:13:24 +02:00
* Begin accepting bugfixes in branches via code review
docs/develop: Introduce release engineering documentation * This has been floating around on trac forever. We should formalize these steps to help future Haiku releases to be successful. Change-Id: I5881e27a23e66a18539d04c5977593a827f8fcef Reviewed-on: https://review.haiku-os.org/c/haiku/+/5441 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2022-07-08 16:01:49 +02:00
* Final translations synchronization
* Generate first release candidates (RC0, RC1, etc), encourage testing.
* Profit
* R1/Beta 2's timeline from branch to release was roughly 35 days
* R1/Beta 3's timeline from branch to release was roughly 50 days.
Release dates can slide, it's ok.
We just try to slide pragmatically (+1 week because of X,Y,Z)
Copy Permalink