Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:36374 php.pecl.dev:5250 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74416 invoked from network); 23 Mar 2008 13:34:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2008 13:34:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=steph@zend.com; spf=permerror; sender-id=softfail Authentication-Results: pb1.pair.com header.from=steph@zend.com; sender-id=softfail Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.150 cause and error) X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 64.97.136.150 smtpout0150.sc1.he.tucows.com Solaris 8 (1) Received: from [64.97.136.150] ([64.97.136.150:11432] helo=n068.sc1.he.tucows.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/AA-10593-A4C56E74 for ; Sun, 23 Mar 2008 08:34:03 -0500 Received: from sc1-out04.emaildefenseservice.com (64.97.139.2) by n068.sc1.he.tucows.com (7.2.069.1) id 4769316E00F90FF6; Sun, 23 Mar 2008 13:33:51 +0000 X-SpamScore: 2 X-Spamcatcher-Summary: 2,0,0,bd1d9992d64733b9,3f501d769369289a,steph@zend.com,-,RULES_HIT:355:379:539:540:541:542:543:567:599:601:960:973:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1515:1516:1518:1534:1541:1587:1593:1594:1683:1711:1730:1747:1766:1792:2073:2075:2078:2198:2199:2393:2559:2562:2693:2895:3027:3352:3865:3866:3867:3868:3869:3870:3871:3872:3874:4184:4250:5007:6119:6261:7653:7875,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none X-Spamcatcher-Explanation: Received: from foxbox (62-31-252-198.cable.ubr07.shef.blueyonder.co.uk [62.31.252.198]) (Authenticated sender: steph.fox) by sc1-out04.emaildefenseservice.com (Postfix) with ESMTP; Sun, 23 Mar 2008 13:33:49 +0000 (UTC) Message-ID: <006d01c88cea$a4319d50$c6fc1f3e@foxbox> Reply-To: "Steph Fox" To: =?Windows-1252?Q?Johannes_Schl=FCter?= , "\"Hannes Magnusson\"" Cc: "internals" , References: <00dc01c88c90$c34c5cc0$c6fc1f3e@foxbox> <7f3ed2c30803230501wc48cb3frda25564f59b32d06@mail.gmail.com> <1206275969.31721.31.camel@goldfinger> Date: Sun, 23 Mar 2008 13:34:36 -0000 Organization: Zend Technologies MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PECL-DEV] About that PECL versioning thing From: steph@zend.com ("Steph Fox") Hi, >> The first step in fixing the core<->pecl relationship? \o/ That's the basic idea, yes. >> But what about extensions that are symlinked to core? Will they need >> to update their version info during core release cycles? >> It obviously shouldn't have a -dev version when distributed with PHP.. >> Is it up to the RM to hunt those extensions down and make sure the >> version info is accurate? > > Just removing the "-dev" in the version number would be wrong (as is > symlinking), a Stable PHP release should include "stable" extensions. > Not dev versions of the extension. So one of the ideas is to fetch the > last stable extension release for a PHP release, but well, then there's > the problem that everybody (people using snaps, people using CVS, ...) > end up with different versions which makes QA hard. (not to mention bug > hunting trouble with people using the latest release but updated a > single extension, ....) But we already have those problems now. Labelling the version just makes it more obvious that we have those problems :) - Steph > > johannes >