Conversation

Notices

1. Embed this notice
   Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Tuesday, 06-May-2025 15:34:12 JST Leah Rowe is not a Rowebot

   https://libreboot.org/news/schedule.html

   I published this a while ago and so far have adhered to it; Libreboot 25.04 came out in April as planned.

   However, I've been thinking further how to implement it. I'll think more about it and issue an update on Libreboot later but basically the plan is this:

   Every release gets a branch. 25.04 has the branch "25.04_branch"

   Any "revision" update releases get tagged in that branch too, and build and uploaded.

   (1/2)

   • Embed this notice
     Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Tuesday, 06-May-2025 15:35:30 JST Leah Rowe is not a Rowebot

     in reply to

     (2/2)

     Stable releases will branch off of testing branches; 25.04_branch is testing.

     25.06_branch therefore will branch off of 25.04_branch when ready, and 25.06 "rev0" (initial release) would be the first tagged commit in 25.06_branch.

     However, the next testing branch will not branch off of stable; the "master" branch will always be a branchless development model as usual.

     So. Master branch, and each testing release branches off of that, in turn later branching into a stable release branch.

   • Embed this notice
     Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Tuesday, 06-May-2025 15:38:25 JST Leah Rowe is not a Rowebot

     in reply to

     (3/2) - because the numbers are never enough.

     Only merge non-breaking changes into a new testing release branch after creation, right up to the release - but the testing branch can also contain a lot more feature changes and such, including board ports.

     A stable release branch would *only* have bug fixes and security fixes in it, no new boards or features; the latter goes in master and in the next testing/release cycle.

     Many projects use this release model, and it'l what I'll use from now on.