Date: Fri, 11 Mar 2016 16:16:11 -0500 From: Ed Maste <emaste@freebsd.org> To: Bryan Drewery <bdrewery@freebsd.org> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: CHANGES file Message-ID: <CAPyFy2Db4eAkjhuvJmSmN=G%2B6z-LV5ka3f1exbPWbb32qkow_w@mail.gmail.com> In-Reply-To: <56E30267.30009@FreeBSD.org> References: <56E30267.30009@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 March 2016 at 12:37, Bryan Drewery <bdrewery@freebsd.org> wrote: > In ports we have an UPDATING file that is targeted at users and a > CHANGES file that is targeted at developers regarding API changes. > > I would like to introduce a CHANGES file as it makes it simpler for > developers to see what has changed without reading through all commit > logs. This is of great benefit for module writers and vendors who may > even have customized some of the code in the tree. Seems like a good idea to me. I worry that it will be forgotten on a number of changes, but that's no worse than today and can be remedied after the fact when a missing entry is noticed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Db4eAkjhuvJmSmN=G%2B6z-LV5ka3f1exbPWbb32qkow_w>