Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63817 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39838 invoked from network); 12 Nov 2012 15:24:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Nov 2012 15:24:47 -0000 Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 209.85.223.170 mail-ie0-f170.google.com Received: from [209.85.223.170] ([209.85.223.170:47932] helo=mail-ie0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/56-05794-EB411A05 for ; Mon, 12 Nov 2012 10:24:46 -0500 Received: by mail-ie0-f170.google.com with SMTP id c12so10440248ieb.29 for ; Mon, 12 Nov 2012 07:24:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JAFtza1KFYjm2Ti4R8VBMD/fo/6BXLToACkIa5OJjI8=; b=lWGRNrCyaKUrJZcxC3Q8AEUIZTLijwKbU0Q+0fh+a0T/3V95FmblQ86iizYnh2fIFs SkDZmJUGDRUPyV3SCtLZEwvddWl0NmqqlbUVGc3Ol19i0p5WZ6JdoGsbtd32GQyVTkfH xqltorTG2tg2Hpjvcu/L7XeuIzWsvYPY/nQhtCocVp/YtAHXAtD6Tm2tS5eFMOiSBETK e1WrZMjza3JG1kuJDLK/00BvIdfK3lJIfbXTSh0l5kvW04CvPJzIk9cFAysFgfA1U/K1 Qb1Sb/iJblMMKldnP7dKyFAL9gqL6ouWpYTHPSRRtJ2rKk3ldT5knaqbbzwG/F4pENb4 w/dg== MIME-Version: 1.0 Received: by 10.50.40.166 with SMTP id y6mr8166133igk.57.1352733883786; Mon, 12 Nov 2012 07:24:43 -0800 (PST) Received: by 10.64.19.148 with HTTP; Mon, 12 Nov 2012 07:24:43 -0800 (PST) In-Reply-To: References: <50A10A9D.9070402@oracle.com> Date: Mon, 12 Nov 2012 15:24:43 +0000 Message-ID: To: Ulf Wendel Cc: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation From: leight@gmail.com (Leigh) Hi, > We put ext/mysql in a (security) bug fix maintenance mode only > years ago. Too many ignore those attempts to get rid of ext/mysql. Maybe it's time to put it into full non-maintenance mode then? I believe MySQL is one of the on-by-default extensions when you compile PHP blindly (as I'm sure many do), why not make it require enabling specifically during build configuration, along with an end-of-script message that states the extension is no longer maintained (not even security fixes). > 2. The next release (5.6 or 6) would add deprecation errors to the code. I think a major version jump would be a good enough excuse to just drop it entirely ;) I'd like to see your list moved up one peg though. If you're going to official deprecate in the docs, why would you wait until the next version to add deprecation notices to the code? In my opinion the more visible we make it now (and sooner we get all of the whining out of the way) the better it will be for all parties. So I'd like to see deprecation errors in 5.5, and removal in 5.6 which is still at least around 18 months away (if we estimate based on the time between 5.4 and 5.5).