From owner-freebsd-ports@FreeBSD.ORG Fri Feb 25 17:53:25 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6DC41065673 for ; Fri, 25 Feb 2011 17:53:25 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A86228FC12 for ; Fri, 25 Feb 2011 17:53:25 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id p1PHrOdt019791; Fri, 25 Feb 2011 10:53:24 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id p1PHrO7u019788; Fri, 25 Feb 2011 10:53:24 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 25 Feb 2011 10:53:24 -0700 (MST) From: Warren Block To: Wesley Shields In-Reply-To: <20100928235321.GB93659@atarininja.org> Message-ID: References: <20100928235321.GB93659@atarininja.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Fri, 25 Feb 2011 10:53:24 -0700 (MST) Cc: freebsd-ports@freebsd.org Subject: Re: Idea: entries in UPDATING for each release X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2011 17:53:26 -0000 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.