Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89767
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFi=Qfbh-yLEdzkX5cxcEqX+kBNhYXVGmoEq+FAdQWipeCKvhA@mail.gmail.com>
References: <0a0a70d756b14a84fc1cd19fd04bb914@mail.gmail.com>
	<CAKws9z2B4KWGOw5_=4CQWe8PxvT2nHf4aKPtPOpnmOhRAKxivw@mail.gmail.com>
	<CAFi=Qfbh-yLEdzkX5cxcEqX+kBNhYXVGmoEq+FAdQWipeCKvhA@mail.gmail.com>
Date: Wed, 9 Dec 2015 07:07:56 +0700
Message-ID: <CAEZPtU44bvn6TrvB0yzjA97JwrNtwi6CLKFnyEr+FS4VzTh7wQ@mail.gmail.com>
To: Adam Howard <oldschooldsl@gmail.com>
Cc: Scott Arciszewski <scott@paragonie.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: PHP 5.6 Support Timeline
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Wed, Dec 9, 2015 at 2:51 AM, Adam Howard <oldschooldsl@gmail.com> wrote:
> #3 all the way.  Extending support only extends the excuse of poor habits
> and encourages those habits.

Same here.

However, if I have to choose something I would like to understand why
all of a sudden December 31 become a valid date. It is unrelated to 7
release date (December 3rd) and has no relevance whatsoever but easier
to remember.

Given this, I would propose to either add, change or update the options with:

-  makes 5.6 deadlines match 7 release date and support lifetime
  . Active support until December 3rd 2017,
  . Active support extended to one year, end December 3rd, 2017
  . And the options for the security support, one or two years

- no change, as stick to what we clearly and openly define in the
lifecycle page (http://php.net/supported-versions.php) and extend
security support to 2 years (ending on 28 Aug 2018)

I had to go with make the dates match with no change, eventually
adding one year for security support as I consider extending the
active support at this stage as a mistake and bad usage of our limited
resources.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org