Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93985
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
To: internals@lists.php.net
References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com>
 <BY2PR0201MB17843F26C4E02181DDDED285BF540@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com>
 <155a8c29-7858-74a6-7c45-5746d79e9a72@gmail.com>
Message-ID: <0003bd10-377a-b3fe-f86a-19bf03eff211@gmail.com>
Date: Wed, 15 Jun 2016 00:04:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <155a8c29-7858-74a6-7c45-5746d79e9a72@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy
 enforceable?
From: rowan.collins@gmail.com (Rowan Collins)

On 14/06/2016 20:43, Stanislav Malyshev wrote:
> And I'm not sure
> how rushing 8.0 helps anything if you're afraid of breaks - you get
> useful features later but also bigger breaks. Long term it doesn't
> matter anyway unless 7.1 is somehow special, which is not. Also, having
> just two minor versions seems to be a little thin, unless there's a plan
> to keep maintaining 7.x, in which case the question is - who's going to
> do that?

In my mind, it's not a case of "rushing 8.0"; it's looking at what 
features we want to release, and how to group and label them.

There seems to be an implication here that if we said we were labelling 
a release 8.0, we'd be *obliged* to break things in it, rather than just 
*allowed* to break them, which makes no sense to me. We're not going to 
run out of version numbers by using them up too quickly.

I think this is where a road map would come in handy; nothing fancy, 
just a list of things that are waiting to get into a release, and maybe 
a general "theme" for each release. If there are lots of small but 
breaking changes coming up, they could be grouped into a release, which 
we would label 8.0. If we want those changes to get released quickly, 
then that release would be soon.

The only difference over drip-feeding them into the 7.x series would be 
that users would know when to expect things to break.

Regards,

-- 
Rowan Collins
[IMSoP]