From nobody Thu Jun 16 16:51:22 2022 X-Original-To: freebsd-hackers@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 778B6846FA1 for ; Thu, 16 Jun 2022 16:51:31 +0000 (UTC) (envelope-from pauamma@gundo.com) Received: from mail.gundo.com (gibson.gundo.com [75.145.166.65]) by mx1.freebsd.org (Postfix) with ESMTP id 4LP7VV1KQ9z4kDh for ; Thu, 16 Jun 2022 16:51:30 +0000 (UTC) (envelope-from pauamma@gundo.com) Received: from webmail.gundo.com (variax.gundo.com [75.145.166.70]) by mail.gundo.com (Postfix) with ESMTP id DA8E54C1286 for ; Thu, 16 Jun 2022 11:51:22 -0500 (CDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Date: Thu, 16 Jun 2022 16:51:22 +0000 From: Pau Amma To: FreeBSD Hackers Subject: RFD: MFC hold time guidelines User-Agent: Roundcube Webmail/1.4.8 Message-ID: <83c320038e43abe1d8bd59b9364a225e@gundo.com> X-Sender: pauamma@gundo.com Organization: The Cabal (TINC) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LP7VV1KQ9z4kDh X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=gundo.com; spf=pass (mx1.freebsd.org: domain of pauamma@gundo.com designates 75.145.166.65 as permitted sender) smtp.mailfrom=pauamma@gundo.com X-Spamd-Result: default: False [-3.90 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[pauamma]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[75.145.166.65:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:75.145.166.64/28]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[75.145.166.65:from]; DMARC_POLICY_ALLOW(-0.50)[gundo.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MLMMJ_DEST(0.00)[freebsd-hackers]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7922, ipnet:75.144.0.0/13, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N https://reviews.freebsd.org/D35405 brought to light the lack of documented MFC hold time guidelines for src (only repo that uses that) beyond: barring critical fixes authorized by release engineering or the security officer, 3 days is the minimum. I'd like to have general guidelines hashed out and added to the committer's guide. To get things started, here's what Ed Maste reported using: instant MFC: security or critical build fixes, or other critical changes, with coordination/approval of re@ or so@ 3 days: straightforward bug fixes or minor improvements where there is a (presumed) very low probability of introducing a regression. e.g. typo fixes, man page updates 1 week: default timeout for most changes with low-medium presumed probability of introducing regressions e.g. adding to a driver's supported devices list, general bug fixes and new features 2 weeks, 3 weeks, 1 month: longer timeouts for changes with increasing likelihood of environment-dependent bugs or unique or rare corner cases e.g. major updates to contrib software, significant rework to kernel subsystems Looking at my commit history over the last several years "1 week" is most common. I used "3 days" and "2 weeks" each about 1/3 as frequently as "1 week." "1 month" and "3 weeks" each about 1/10. Sometimes the MFC timeout will be longer or shorter than I would otherwise choose in order to exclude or include the change from an upcoming stable/ branch. For context: git log | grep -i -E 'MFC.*after.*:' | sed -E -e 's/^ *(X-?)?//i' -e 's/^MFC[a-z0-9]*[- ]after: */MFC after: /i' | sort -fb | uniq -ci | sort -bf -k 1nr 19169 MFC after: 1 Week 11807 MFC after: 3 Days 10941 MFC after: 2 Weeks 4002 MFC after: 1 Month 1919 MFC after: 3 Weeks 838 MFC after: 5 days 643 MFC after: 2 Days 621 MFC after: 1 day 407 MFC after: 4 weeks 346 MFC after: 2 months 322 MFC after: 7 days 282 MFC after: 4 days 281 MFC after: 10 daysbnb 222 MFC after: 3 Months (cutting off at <1% of the most common hold time) for all committers is similar to Ed Maste's. So what do others think? If and when consensus emerges, I'll write it up for possible inclusion in the committer's guide. -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila)