From owner-freebsd-hackers@freebsd.org Sun Jun 23 19:52:33 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 244C115D92D6 for ; Sun, 23 Jun 2019 19:52:33 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail0.glenbarber.us", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50DAC6CE6D; Sun, 23 Jun 2019 19:52:32 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from [192.168.1.17] (24.102.164.36.res-cmts.swb2.ptd.net [24.102.164.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 2CF321E1CD; Sun, 23 Jun 2019 19:52:31 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 mail0.glenbarber.us 2CF321E1CD Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: release notes file From: Glen Barber X-Mailer: iPhone Mail (16F203) In-Reply-To: <6B485E5C-9C8A-43C8-BD5A-528A74A61A23@FreeBSD.org> Date: Sun, 23 Jun 2019 15:52:30 -0400 Cc: freebsd-hackers@freebsd.org, re@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <79B7AEEE-7617-44D8-A16A-C8EC5F95455A@FreeBSD.org> References: <20190623191818.GA84365@raichu> <6B485E5C-9C8A-43C8-BD5A-528A74A61A23@FreeBSD.org> To: Mark Johnston X-Rspamd-Queue-Id: 50DAC6CE6D X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.97)[-0.973,0]; ASN(0.00)[asn:36236, ipnet:2607:fc50::/36, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2019 19:52:33 -0000 FWIW, I don=E2=80=99t think =E2=80=9Ceither/or=E2=80=9D is necessarily the b= est approach; meaning I would like to still keep the tag in the default temp= late. Glen (Who knows first hand how much it sucks going through commit logs for relnot= es entries) Sent from my phone. Please excuse my brevity and/or typos. > On Jun 23, 2019, at 3:49 PM, Glen Barber wrote: >=20 > Yes, please. >=20 > Glen > Sent from my phone. > Please excuse my brevity and/or typos. >=20 >> On Jun 23, 2019, at 3:18 PM, Mark Johnston wrote: >>=20 >> Hi, >>=20 >> Today we add a Relnotes tag to commits that warrant a release note. >> My impression is that it doesn't work so well: if a committer forgets >> or doesn't know to add one there's no way to amend the commit message >> (same for MFCs), and a commit message isn't a convenient place to write >> the text of a release note. I would like to propose adding a top-level >> RELNOTES file instead, which like UPDATING would document notes for >> specific commits. It would be truncated every time the head branch is >> forked, and changes to it would be MFCed. This fixes the >> above-mentioned problems and would hopefully reduce the amount of time >> needed by re@ to compile release notes. >>=20 >> For example: >>=20 >> Index: RELNOTES >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- RELNOTES (nonexistent) >> +++ RELNOTES (working copy) >> @@ -0,0 +1,8 @@ >> +Release notes for FreeBSD 13.0. >> + >> +r349286: >> + swapon(8) can now erase a swap device immediately before >> + enabling it, similar to newfs(8)'s -E option. This behaviour >> + can be specified by adding -E to swapon(8)'s command-line >> + parameters, or by adding the "trimonce" option to a swap >> + device's /etc/fstab entry. >>=20 >> What do folks think? >>=20 >=20