Date: Fri, 8 May 2026 13:10:30 -0700 From: "Enji Cooper (yaneurabeya)" <yaneurabeya@gmail.com> To: Renato Botelho <garga@FreeBSD.org> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-current@freebsd.org Subject: Re: Update strategy and timing Message-ID: <A33302A4-DEC5-41C4-BBD2-0ABA1AA3CA95@gmail.com> In-Reply-To: <9ed12219-6e78-4156-b0df-aca91a732127@FreeBSD.org> References: <af4FwVaA_3P4yam-@www.zefox.net> <9ed12219-6e78-4156-b0df-aca91a732127@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > On May 8, 2026, at 9:37 AM, Renato Botelho <garga@FreeBSD.org> wrote: > > On 08/05/26 12:48, bob prohaska wrote: >> Is there a preferred strategy to timing updates >> for self-hosted FreeBSD systems? >> On the stable branches it's easy; just update when >> updates are announced and build/install. Once caught >> up, things can be left alone for days at least.. >> With -current there's essentially no pause in the >> stream of fresh commits, so git finds a new commit >> by the time buildworld finishes. >> Is there some marker or indicator that signals the >> -current tree is at least nominally consistent and >> buildable? I'm not asking if it'll work, just whenter >> it's worth a try. >> For example, my practice has been to run git pull, >> then make buildworld. If buildworld succeeds, I'll >> try another pull. If nothing new shows up then run >> install and reboot. This works with a stable branch, >> but with -current there are always fresh commits. >> I've tried looking at the commits to see if they're >> relevant to problems I'm seeing, rebuilding if they >> are and proceeding with install if they seem unrelated. >> Is this approach at all sound? Is there a better way? > You can follow the stabilization week mark. More information at: > > https://wiki.freebsd.org/StabWeeks +1 to what garga@ said. Generally following the “post-stab week point” is the best way to handle things if you don’t have the cycles to debug/triage new issues. If you have any suggestions for missing tests to make your upgrade experience smoother, please discuss them in a new thread. We can get the proposals entered into Bugzilla and hopefully handled in a timely fashion (if the scenarios you’re requesting are easy enough to implement and make sense to cover in a universal manner). Cheers, -Enji [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkHfexGRJ3gYRdA2gGpE5DjPsNJgFAmn+QzYACgkQGpE5DjPs NJgZmhAApcK+pUo50Q671Eimn3hTy5vjBzEoDq2HxFCMOr3yICzfBhvntEX3eilT tsUUK1lnwiMldWmKLC2P7FSfqiYXR4sIFI6L5t0YM93Nq2qMgeMtW5ML1+RSiIpo BpM55+kDgtiSPpJIkkvqx2SotrOB+NFmG7+nNcKwvbrGL2yb+3wSk6wkONCNQG6f raVULarny6FBYittRJ7UdfEs4PgP4axh1n2K25lkHUVfLbk1QSDXYpUZ6+zysr1h 4U5KW9WnqONBp0WGj0dVflNIbwTuaTYqdy4UXHnrL7P0nLYCTJ3gguRwpLVWWWpf JlJR7ai6Lwlioci7069hsBOy2JLHuZQMl3gB9knu7AvZPltsuRVuuXoe2+lu/1vz FyznX3uLhqd6kiFYjPOxTyVkUUxW/X8VXOvUiu57o5gpy2p/Nh4potcjz1AI3Rqm QhuIRILAincEq1+UsEsbEZAnzYC0d7By/t/ookiY/Lo5jCXhrMzE1isJkkgOY2R0 itGOtPghcOTNA6YHUG8QUyek2lMuVeV1x35G3q2TQ64VvAEWzAg2T9FiQHjavz2m dhf8rOFR3/UmjIQo99xDaaf7vULQQQy7FcDpOlpA6rlCJd0EKroqOw9aX2ElsR9f sh96tIzsxehxAN85nxpPCH7d7kA7ZMnTOa/NAnPKogAkKTQax/Y= =UQ15 -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A33302A4-DEC5-41C4-BBD2-0ABA1AA3CA95>