Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28053
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <45D5858B.8020103@zend.com>
Date: Fri, 16 Feb 2007 13:20:59 +0300
User-Agent: Thunderbird 2.0b2 (X11/20070116)
MIME-Version: 1.0
To: Hannes Magnusson <hannes.magnusson@gmail.com>
CC: php-dev <internals@lists.php.net>
References: <45D47062.1010405@zend.com> <45D4DCF3.2050007@zend.com>	 <7f3ed2c30702151432i50f94ffarbb6459791a57149f@mail.gmail.com> <7f3ed2c30702160200q2aa8cfb5t845d43742c5125f@mail.gmail.com>
In-Reply-To: <7f3ed2c30702160200q2aa8cfb5t845d43742c5125f@mail.gmail.com>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RC announcements at php.net
From: antony@zend.com (Antony Dovgal)

On 02/16/2007 01:00 PM, Hannes Magnusson wrote:
> So, here is my left handed pet dwarf turtle, born in December, idea:
>  It doesn't really see the point of scattering boxes all around. One
> box listing current php5 + php4 version and the current release
> candidates should be all that we need.
> The RC links obviously won't be direct links on the tarballs so the
> user still has a chance of understanding "wth is RC?".
> 
> The release candidate links will point to qa.php.net/#v5 & #v4 where
> we'll add a big fat box explaining the concept of release _candidate_.
> The stable links then point to php.net/downloads.php#v5 & #v4
> 
> The only "major" change is how RM will post a new release; this patch
> expects all current (stable and (if any) rc) in include/version.inc
> 
> See attached, simplified, patch & screenshot:
> http://home.oslo.nith.no/~maghan/releases.png

Looks great, but I would like to divide it into two parts:
1) Releases
2) Release Candidates (which would disappear when there are no RCs).

-- 
Wbr, 
Antony Dovgal