>jeu. 12 févr. 2026 at 09:41, Vagrant Cascadian <[email protected]> wrote:
> On 2026-02-12, Cayetano Santos wrote: >>> A rough proposal for how this would work: >> >>> 1. Developers push to a new branch (e.g. 'main') >>> 2. CI builds each commit >>> 3a. If the build is successful the commit is updated on master >>> 3b. The substitute from the build is available to users >>> 4. User pull down from master receiving the new commit and any associated >>> substitute >> >> The simpler, the better, with no overload for anyone. >> >> What about ?: >> >> 1. Developers push to devel >> 2. CI proceeds as usual >> 3. Master mirrors devel, delayed by one week >> 4. Users pull down from master, as usual, optionally from devel >> >> Just simply: developers proceed as usual, and they have one week to fix >> problems; ci has one week to build substitutes; users always have >> binaries available. >> >> No new tooling required (other than the delayed mirroring of devel to >> master). > In a world without security updates, that sounds pretty good! :) > I suspect there are other corner cases, too... though that is the first > that came to mind... I implicitly assumed that security updates land to master, so its name (as opposed to devel). Master might be daily merged to devel. > What happens if there are unresolved issues after a week? I guess no > worse that the current situation of pushing directly to master... You can deliver everything, all the time, right away, as we do now, accepting its advantages and inconvenients; or you can delay delivery around 6 months, being conservative, which presents other advantages, ... but you’ll have to figure out how to live with a different set of inconvenients. Or you can do something in between, meaning reaching a compromise between advantages and inconvenients of each alternative. One week is a cursor to be fine tuned, in a seek for optimisation between pros and cons. > I suspect you'll get a fair amount of "developers only following devel" > with a bit of a "works for me" feel, other folks only finding more > issues once it lands in master... For sure, you can even imagine people switching hourly between branches. But with increased degrees of freedom, comes greater responsabilities. All in all, you’re probably right, and a testing period would be necessary. C.
signature.asc
Description: PGP signature
