From nobody Fri May 8 20:29:50 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gC12M3VKgz6cw4y for ; Fri, 08 May 2026 20:30:03 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic308-55.consmr.mail.gq1.yahoo.com (sonic308-55.consmr.mail.gq1.yahoo.com [98.137.68.31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gC12M18N2z3rdb for ; Fri, 08 May 2026 20:30:03 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1778272196; bh=7QAJJf/DsVe/osZYWTTL6cZ/PeuXjjz6oGTpU2hHT0E=; h=Date:Subject:To:References:Cc:From:In-Reply-To:From:Subject:Reply-To; b=IZNQHaNND6EzfL3gnG8jrP5uv1uMGmSsqb0kUAfBZEMzNpMoZl5flsrwuDouAfoQ5OmaASCbSIw6E+ZfAusgDMQTPBpYwEcoX5kIorvc7a9lHaFeasawCSjwymSPWUm1GTdg7k0tlb326wDB87dAStsGSkMv665lgQzSPyGOzON2ws3wiURUYcNgxiwOcHbyjx4OHbkMsOGm5O1n1rW+0VXQiD7NifJ3IKMHF5/GMKuuEYj8FdZx7/LOV+V1nkrR87GQ7CYM/isMtggSUJM+VavTWE4Fel7UBkhEplKgGsN/eET0vSmupWvTfh9L5J+BAkNCiO/gaIVSR6gj/PTcvg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1778272196; bh=2iIGeFGZ9T/QfzHrxLAIytbGa4TV6yO5tiHfL+nbdn+=; h=X-Sonic-MF:Date:Subject:To:From:From:Subject; b=fBxr/scoT4aZKbhc2n6sDZWvfn5WfsJc/YDX3DOjx5GgyxTYoYbR3PMe+k03P4rLAHyRlVT2JXVEX04T3axbiiuZ5Ki8zIRbm5i3qpYNL84n+fDLHl0XY8d9Ko/vFXF4nwkrdiefgvVurbxMKUOUJ+juq6DP6K22V1Ph+vQXe71sRH9NjesC96LERhTk7pi1KNGG6TGND0kqnBFNa/8C9bbhkc16aHtw1pwYH+KqH/YolkqcFcgN+P1tUzt+8zcMLXy1JRAeNDR3XXeKagNG8uB3184jF0AAyWgBDBeKc7MyDB/fdkXVWQBdIMyUk1T246DAkTemNf/6kx2yhjyiUw== X-YMail-OSG: JMCkSuEVM1m0P8njTCL1BwwBq9YNQLVHxSBo14qYWkPQ7lI5EwyS3hrG2V4o4pi hkYArCK_eRfWGrY_tnVUofCPIXcG9SaDuYeApp8BkiIibk16vDFxCaSaxwEfwDLk2Lno5evvPX71 JiVrSdPBTg7e_cWAJFLga8vpNtAeh9UNDuNngxLV8pyr2nrZ0VlmT.GuGMxhnTcrEz5aRlkXbK_8 PaaXX7msw44Jg2L1d_cnWUiR01WSXYF93zBgTLvUyMcmoDGJntxHvPpG1mVuyqwcf.K8minPCjam Tlx8sTpmQvS_85_01vHdOH.WShUN8ChtX9jGMljSqG9iR4VZJUVQZROPAHJ0bLTdG9ImZS6OaAZq g933bziynqmeQ_Jq3Gcet5o_VmupdDbD6Kps6eYRB0n86_8qOxyXcQjr3i3ih3h.Cl8d8f4T0OW6 UwjylQ.zz3Pbxi9C5MwcBZSfaWWFYAu4trzn9o7bB5YtZ3RTqlu.IEefKmge4wIMMhc.TfFiDtkk Z9qVccb2304lj85rnqAKN9OeWxEJ18f2tDB6DflilGL3VptYXYralR0LSOYTJNgdWd7vFXdDvvhl hq_ipOOTMmgU38jCwcZomrhx_z7sdCg9mGwM.88gbbcz28RcRGU80pxK_ebsBEC2qYIAYxEV42Ai uhPWKsUhZ3c.zimVAuMY7i858Q1OvtIu6Ycu1yhp.cDTGMXqANxJmJcc1YAY8aflBybRdPqnaL6U CGsdMGDhvsEzt85jiafu9o9l8Kwk6FcF824UbTbtxCTne.gi3rxWyxgamQEO8JsVTyMKPg4TISJy IWu.gWRT8Xo3SMrZzd.5CyjqFocVuVX2gqXvvv9seBBPh.PBl3Oie5wEHGrRq6u5hZXSyG9_hMKX S8ifKttytsB2HT8kj917vhh5In2JWRlz3W65RpJqlKaJ.t1jraHUxqvo_aCSf15Z7aQ4iVAq8wRI kpxtJAdqomsfsxywXPhJyHKjP0TvY9Fp9tG_NZMDzsrp8SE8YSYkti4jLYCX4PhUNW...KMwM..Y 3oYo09atHUAtHh5DkQMMRbiMrhJSgXD4vtcCcLFoGx4IuuxGajT0Rn16tMogthJo1z75x3GPKpTK mSq3thkAvBHeia2ZrLr0a88ZKIjvP8fDQDKLrRQf4.UlbOeZqeMOuZVM7wOcTWyF5hocf7MtOQAl J6h7tpY.v.T0.EGfqzF5KHe7JqSPb4Pj41ctSF7qB7Gc8M.NWPAmq7RqkA3mMb.aY2Bp59yEm9H4 dI7itMZ3iLCaGZ2OfklimnHKg5t_IUxWsmA327XcfbV7VLkRrnT.m3wgQA6G8NdQna4dYoFOSZey grGKY4BnO2sOJ4yfX4D0S8PzFJeVibtUlzy7yAq3m0incIYXlv0c5QQcMyn9wXmEcb0S8xwnc2mV GSU4pVhHdIblagHsnPI7VX0R3Qqovi7CzcW2M0B0hJ5vkrS4hSQWYedS8zTQnawd_6De2NHJnpvx xbaSzlRVsrE_SXBlL0q1zv2nda5n3m1ZwqbelZ3aj2D7kvSkL0.PxdKQ07rbnjwKfHYsp4fjMwKH oo4E6y.Qa6bNsanZqgmSJVVTpiCSjOK1d5TYrXw79TijdTNUpA79MK17K6PRBChCB07uKfmrpsX. rFCBZjb9MdwsY5JO1Dcv_F3_ie2WBmVkO4zsJ9v8aS8x4QwGy2twdmxTJ2Oz6.WqyWBVjPZ7lE6a 36EKNjnLdBzMCTgD.P0rOCfzSWlG3woRuiOL8xH25sp0jZogqzyvFH4Fxfm52Qe8o36ujGYJiicR L.ZHqveUy_UQxD_XQkdZYMk9Qmi_dADbgaEHV9hn5RSo531FEjGRvVyO3zOc25Z6mmssobHZD7W1 Wkpk1g3mCApNOeCL8EsrRXvr4zVb_rzWVBdmcCzcVSCRZLbhmtVzg3RGwTHQP52WqVzYdxVQFq_l wiuY_QEXWF0zYyFtN0UUgWRop1rtESy05cMHX3jU8Q5mZ6teJol8zEtKfqni5obSVOe6QjhayhVw R2SVpdkcPzL3FRlG9FWTZbeNw5NBefARFnSzD1O2mLw64iJi2wtOn_ZRtYHE6NjXWPp1BCkms65R 0wqP0izEF9kqPYi2MP8EkqATV17iMyYy4FQVY5nARpNU1PUHUOmooUcN_RNBiYNEPdMY0YYaIkYO 3RxuAZFSQ2tkC288s6IV6cZLHabWBhYGBLWZjUbaID0iDw4FhiqMrHT8szZ1SW3G9AL16bSqgc6O ldtO1GvQ9PqR50e0r7ituY0wIVnLSCXDpn9R4kZ6OD7ckPitXXYp35LSmS0QTDO5s1eOdIKojnMm WSFbqG9_KgXJUGVVKcrAngPrw8yjEv3ZGu_jwZEq5tssAIW.BqxkLOA1EDw-- X-Sonic-MF: X-Sonic-ID: 54a5f445-8616-4a42-8cda-2dd648af52e6 Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.gq1.yahoo.com with HTTP; Fri, 8 May 2026 20:29:56 +0000 Received: by hermes--production-gq1-7bb7df5c46-cpn2t (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 144fc29d602d1eda3b5a91d0b5cf2ef3; Fri, 08 May 2026 20:29:51 +0000 (UTC) Message-ID: Date: Fri, 8 May 2026 13:29:50 -0700 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Update strategy and timing To: bob prohaska , freebsd-current@freebsd.org References: <9ed12219-6e78-4156-b0df-aca91a732127@FreeBSD.org> Content-Language: en-US Cc: Renato Botelho From: Mark Millard In-Reply-To: <9ed12219-6e78-4156-b0df-aca91a732127@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Mailer: WebService/1.1.25725 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4gC12M18N2z3rdb X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On 5/8/26 09:37, Renato Botelho 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 > Note how this example would work by you [Bob P.] choosing to use somewhat older vintages that have been separately tested --based on the test results indicating evidence of some stability for your workload. That is instead of using the most recent commit that have not had later, separate testing. The details of the specific testing seem unlikely to be biased to issues more specific to armv7 on RPi2 v1.1's or aarch64 on RPi4's, RPi3's, and RPi2 v1.2's. I've no clue how the testing would fit with your networking context. The testing is generally monthly. (2024-Dec was canceled, for example.) "* Last week of a month is declared a stabilization week . . . For our purposes we will use the week that contains the last Friday of the month." Also: "Monday 8:00 GMT a tag is created and published. Right now it is published at [the glebius] personal https://github.com/glebius/FreeBSD/tags. Note that the tag points at a hash in the official repo, so there is no trust involved here." More from: QUOTE of what glebius wrote: At the end of the stabilization period be it Friday or earlier I will write email to current@ reporting the results: - were there any regression identified with the Monday tag - what has been accumulated in the stabweek branch - known stable point(s) of FreeBSD/main during the period, recommended for use The free riders who did not participate in the testing are now welcome to update their machines to published stable points :) More seriously speaking, I actually hope that in some future snapshots.FreeBSD.org will start using these points for snapshot generation. END QUOTE As far as I can tell, use of stable points when fix hashes are involved means git branching at the (final) Start hash and then cherry picking the fix hashes for the Start hash into that temporary(?) branch: the result is not at some commit that is directly on main. (main could have had other changes mixed in that were not tested.) So it is biased to folks that use git somewhat more like a developer. Sometimes there is a "use hash" from main instead of cherry picking. The freebsd-current message closing the stabilization week is essential to giving context about what to do. I do not know how this fits with what you are comfortable doing. -- === Mark Millard marklmi at yahoo.com