Date: Sun, 23 Jun 2019 15:52:30 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Mark Johnston <markj@freebsd.org> Cc: freebsd-hackers@freebsd.org, re@freebsd.org Subject: Re: release notes file Message-ID: <79B7AEEE-7617-44D8-A16A-C8EC5F95455A@FreeBSD.org> In-Reply-To: <6B485E5C-9C8A-43C8-BD5A-528A74A61A23@FreeBSD.org> References: <20190623191818.GA84365@raichu> <6B485E5C-9C8A-43C8-BD5A-528A74A61A23@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <gjb@freebsd.org> 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 <markj@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79B7AEEE-7617-44D8-A16A-C8EC5F95455A>