Re: RFC: ext/mysql deprecation
| From: | Pierre Joye | Date: | Mon, 19 Nov 2012 12:54:07 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63970@lists.php.net to get a copy of this message | ||
hi Anthony,
On Mon, Nov 19, 2012 at 1:44 PM, Anthony Ferrara <ircmaxell@gmail.com> wrote:
> Adam,
>
> My intention at this stage is to call a vote next Monday: it feels
>> like the discussion has mostly died down now (which isn't to say I
>> think we're at a consensus necessarily — it just feels as though the
>> flurry of opinions have been made and argued either way), and I'm
>> hoping that everyone can have a think about where and how they'd like
>> to see this move forward (if at all) between now and then. Given we've
>> only just hit alpha 1, I don't think we need to rush into a decision
>> right now for the sake of one.
>>
>
> I completely agree.
>
> I would suggest one thing though. When it comes up for a vote, please
> either make 2 questions:
>
> 1. Should ext/mysql be hard-deprecated in 5.5
> 2. Should ext/mysql be soft-deprecated in 5.5 and hard-deprecated in NEXT
>
> Or 4 options to deprecation:
>
> 1. Hard-deprecated in 5.5
> 2. Soft-deprecated in 5.5 and hard-deprecated in NEXT
> 3. Either
> 4. Neither
>
> That way both viewpoints can be voted on in one vote. And we can get an
> accurate count of the thoughts...
Hard/soft deprecated?
I suppose by "soft" you mean not actually deprecated but only
documented as such?
The on connect only notice is rather soft, tbh :)
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org