Date: Fri, 25 Feb 2011 10:53:24 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Wesley Shields <wxs@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: Idea: entries in UPDATING for each release Message-ID: <alpine.BSF.2.00.1102251051200.19767@wonkity.com> In-Reply-To: <20100928235321.GB93659@atarininja.org> References: <alpine.BSF.2.00.1009281157040.99985@wonkity.com> <20100928235321.GB93659@atarininja.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Sep 2010, Wesley Shields wrote: > On Tue, Sep 28, 2010 at 12:07:08PM -0600, Warren Block wrote: >> Right now, people who install ports from a -release CD and then start >> upgrading don't have a clear marker for how far back to go in UPDATING. >> >> A simple entry would be enough: >> >> 20100703: >> AFFECTS: >> AUTHOR: >> >> FreeBSD 8.1-RELEASE >> >> Not sure what AFFECTS should say. There might be other useful >> information that could be included in the note. Comments? > > I'm certainly not opposed to the idea but what exactly do we use for a > date? When the tree is tagged? When the release media is finalized and > published to mirrors? What about tag slippage? Do we account for that? > > If the only goal is to get a rough idea of when a release was cut then > either when the tree is tagged or when the media is pushed out to > mirrors is probably sufficient. Based on what I saw with source, a 20110224 8.2-RELEASE entry should be just before the 20110224 entry for net/openldap.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1102251051200.19767>