Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id B2D0F9FC081 for ; Thu, 22 Feb 2007 19:49:47 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 75379-01-10 for ; Thu, 22 Feb 2007 19:49:41 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by postgresql.org (Postfix) with ESMTP id 407E39FC044 for ; Thu, 22 Feb 2007 19:49:41 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id k3so227588ugf for ; Thu, 22 Feb 2007 15:49:39 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p4ltKzrT/EUfPXbtLpAB1aZQsK0DJ+pcpCKaMhjQ2s53nspmaMP6H6T31yLuKia57HHzzwP+cYiBYorSiYmrdyEHYA7RsOcgSY3EBCi6kggDUQPxeeN2ngvZiQp5L60+wOOT7IZ66niMlP8QC8fQqvxAer56THvxgKMaN05cvk0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JHgz7ggAaRwU0V9fuwv8WppDaGwJv6M9CJL5oYL4rP/hgtFaHU88yC1+CG6IQ0OI1MJAJmCBRqJXGLqHwOLgXvyz6jmleyqxiDcdTgk0hnb6CQugzrL3R7HlrcHbB12xWgs0tdtKqwqYJggkwJMpVZNxtqfhtyiFv/jmoHkePzk= Received: by 10.114.153.18 with SMTP id a18mr576075wae.1172188178341; Thu, 22 Feb 2007 15:49:38 -0800 (PST) Received: by 10.114.132.17 with HTTP; Thu, 22 Feb 2007 15:49:38 -0800 (PST) Message-ID: <5a0a9d6f0702221549x3c5acab0k5ada06a76bb6686a@mail.gmail.com> Date: Thu, 22 Feb 2007 15:49:38 -0800 From: "Andrew Hammond" To: "Joshua D. Drake" Subject: Re: [DOCS] should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them? Cc: "Magnus Hagander" , "Bruce Momjian" , pgsql-docs@postgresql.org, "PostgreSQL www" In-Reply-To: <45DE2AED.1040306@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070221144716.GA21044@svr2.hagander.net> <200702211507.l1LF7Me12089@momjian.us> <5a0a9d6f0702211113v740f5014m6e1df594303196b2@mail.gmail.com> <45DD8E15.2050006@hagander.net> <5a0a9d6f0702221541x71705642if61ab67ef32d6cdb@mail.gmail.com> <45DE2AED.1040306@commandprompt.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/244 X-Sequence-Number: 11649 On 2/22/07, Joshua D. Drake wrote: > >> > On the front page, we already have "Latest Releases" with links to the > >> > most recent release for each version still actively maintained and > >> > release notes. (Would it make sense to change that title from "Latest > >> > Releases" to "Actively Maintained Releases") > >> > >> I think not. The meaning is "latest releases available for each branch", > >> not "these are the actively maintained branches". > > > > Why aren't 7.3.18, 7.2.8, 7.1.6, etc there then? > > > > Clearly there is some criteria for which branches are presented there. > > <7.3 is EOL. We still back patch what we can but they are considered > deprecated. Yeah, I figured that was the criteria. So, is it not reasonable to say that the releases listed on the front page under "Latest Releases" are actually "Current minor release for branches which have not reached EoL"? Perhaps instead of "Latest Releases" or "Actively Maintained Releases" something like "Current Releases" says that better? Andrew