Problem
promote-snap-train (justfile) promotes every track from edge straight to stable on a daily cron, with no age check. For the latest track, if the version being promoted is a new .0 patch release (i.e. the first release of a new upstream minor/major version), this can push an untested release to stable the same day it lands in edge.
Proposal
For the latest track only: if the revision in edge is a .0 release, only promote it to stable once it has been sitting in edge for at least a week (or matches whatever soak period upstream uses for that release, if longer).
Non-.0 patch releases and older tracks keep the current same-day edge → stable behavior.
Why
Gives .0 releases, which carry the highest regression risk, a minimum soak time in edge before reaching users on stable.
Problem
promote-snap-train(justfile) promotes every track fromedgestraight tostableon a daily cron, with no age check. For the latest track, if the version being promoted is a new.0patch release (i.e. the first release of a new upstream minor/major version), this can push an untested release tostablethe same day it lands inedge.Proposal
For the latest track only: if the revision in
edgeis a.0release, only promote it tostableonce it has been sitting inedgefor at least a week (or matches whatever soak period upstream uses for that release, if longer).Non-
.0patch releases and older tracks keep the current same-dayedge→stablebehavior.Why
Gives
.0releases, which carry the highest regression risk, a minimum soak time inedgebefore reaching users onstable.