Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61816
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.155 as permitted sender)
Message-ID: <50117227.7090709@sugarcrm.com>
Date: Thu, 26 Jul 2012 09:36:55 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= <johannes@schlueters.de>
CC: PHP internals list <internals@lists.php.net>, 
 Stas Malyshev <smalyshev@gmail.com>,
 David Soria Parra <dsoria@gmx.net>
References: <1343317268.1801.55.camel@guybrush>
In-Reply-To: <1343317268.1801.55.camel@guybrush>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Release Frequency, NEWS, etc.
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> The current idea would be to skip every second release (unless security
> issues demand something else) both in release date as well as version
> number. So for instance 5.4.6 will be released sometime next month
> alone. A month later there will be 5.3.17 and 5.4.7.

I think it makes sense.

> 
> Doing this has an obvious issue, though: NEWS entries are currently only
> placed in the lowest branch. With the example from above and the current
> way the NEWS are handled 5.4.6 NEWS would be quite small and there would
> be no 5.3 NEWS to check for further things.

I think note in the NEWS should be placed immediately when the bug is
fixed (at least the lowest version NEWS). However, if we want the bug to
appear in all NEWS for both 5.4 and 5.3, I think we'd have to ask people
to put note in both. I, on my part, am reviewing NEWS periodically and
merge entries that I can find that are in 5.3 but not in 5.4.


-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227