Date: Wed, 31 Jul 2019 23:13:51 -0400 From: Ed Maste <emaste@freebsd.org> To: "Rodney W. Grimes" <rgrimes@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r350505 - in head: contrib/binutils/binutils/doc gnu/usr.bin/binutils/objdump Message-ID: <CAPyFy2Bj=2gaeXMA1AsFLX2=vmUjW2sEa9ugN00AzvAjqvZouw@mail.gmail.com> In-Reply-To: <201908011650.x71GoxBe060563@gndrsh.dnsmgr.net> References: <CAPyFy2BpPbQ%2BXynADKzeraVnLXPuzm-ohM7uigMc-7S6Ly4YXA@mail.gmail.com> <201908011650.x71GoxBe060563@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 1 Aug 2019 at 12:51, Rodney W. Grimes <freebsd@gndrsh.dnsmgr.net> wrote: > > That would be fine, the important thing is that the > r350505 gets listed in the file, I don't see any reason that r350505 specifically should be in a release note - this is a minor clarification of an existing deprecation notice. It seems having an overall "deprecation notices" section in the release notes would make sense, but they should really persist from version to version. Should we add a top-level DEPRECATION_NOTICES file perhaps? Or tag deprecation notices with some sort of comment in the source so they can be found with a 'grep' during release preparation?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Bj=2gaeXMA1AsFLX2=vmUjW2sEa9ugN00AzvAjqvZouw>