parent
5662b578d8
commit
62b5b1950e
|
@ -398,27 +398,8 @@ the [Libreboot 20241206 revisions page](libreboot20241206.Revisions.md).
|
||||||
Formalised release schedule
|
Formalised release schedule
|
||||||
=================
|
=================
|
||||||
|
|
||||||
We normally just do a release and that's it. It's still tentative, and this
|
UPDATE: the text of this section was removed on 17 January 2025.
|
||||||
may change, but it has so far been decided that the 2025 release schedule will
|
|
||||||
look like this:
|
|
||||||
|
|
||||||
* April 13th: testing release
|
Please read the following new article instead:
|
||||||
* June 12th: stable release
|
|
||||||
* October 31st: testing release
|
|
||||||
* December 6th: stable release
|
|
||||||
|
|
||||||
Where any release is made, revisions such as today's 20241206 revision 8 can
|
[Formalised Libreboot 2025 release schedule](schedule.md)
|
||||||
be re-released. On stable releases, only the most desirable improvements and
|
|
||||||
fixes will be made, without substantially altering the substance of the
|
|
||||||
original release, while testing releases can have wilder revisions; where the
|
|
||||||
current release is a testinng release, revisions should be frozen in place
|
|
||||||
about 1 month before the scheduled stable release.
|
|
||||||
|
|
||||||
This is preferable because it offers much more flexibility, and it means that
|
|
||||||
stable releases can be closer to upstream whereas previously they'd be
|
|
||||||
about 3-6 months behind, e.g. the Libreboot 20241206 release uses coreboot
|
|
||||||
revisions from the summer of 2024, but some of them are closer to December
|
|
||||||
of 2024.
|
|
||||||
|
|
||||||
This was decided, ever since the 20241206 release, which just so happened to
|
|
||||||
compliment a 20240612 release. Symmetry is good, as is predictability.
|
|
||||||
|
|
Loading…
Reference in New Issue