Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15726 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73554 invoked by uid 1010); 2 Apr 2005 01:51:05 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 73539 invoked from network); 2 Apr 2005 01:51:05 -0000 Received: from unknown (HELO gmail.com) (127.0.0.1) by localhost with SMTP; 2 Apr 2005 01:51:05 -0000 X-Host-Fingerprint: 64.233.170.199 rproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.170.199:31397] helo=rproxy.gmail.com) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id 87/FD-22409-88AFD424 for ; Fri, 01 Apr 2005 20:51:04 -0500 Received: by rproxy.gmail.com with SMTP id b11so833341rne for ; Fri, 01 Apr 2005 17:51:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=hKnavL8F9ZbV8olodi4DF96VFgu6BAxVr8MR4o3I0X9RtW1jyHGCnCZXt/KLFVNlqNbfLyWOwLtx/M5Ca99M0quW2Jv7J2FyCJ3XraQ7THo2/UhoDyFaRgxgKwSqeoHEcmAWgtbXBSSJrtJ+KQJ3s3lGs1wQ1mxQIoFcXMwXGhc= Received: by 10.38.87.21 with SMTP id k21mr3255126rnb; Fri, 01 Apr 2005 17:51:00 -0800 (PST) Received: by 10.38.86.51 with HTTP; Fri, 1 Apr 2005 17:51:00 -0800 (PST) Message-ID: Date: Fri, 1 Apr 2005 20:51:00 -0500 Reply-To: James Ellis To: internals@lists.php.net In-Reply-To: <001f01c53722$e7ad30b0$6401a8c0@mwindows> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <5.1.0.14.2.20050401235721.0668c050@localhost> <001f01c53722$e7ad30b0$6401a8c0@mwindows> Subject: Re: [PHP-DEV] PHP 5.0.4 PEAR issue From: james.ellis@gmail.com (James Ellis) Hi I think a 5.0.4.1 would be the best way to go (not sure what versioning to use), as there are no real code changes to justify a 5.05. You could then provide a patch with notes for those with 5.04 installed or they could compile 5.0.4.1 I'd suggest if you rerelease the 5.0.4 as "5.0.4" then those with 5.0.4 installed will become a bit confused as to what they have installed (unless they do the checksum check). As for the CVS issue, I find in the code I write, doing a "cvs diff ." on my local directory tells me if anything is not in the repository, then I can cvs add and cvs commit once done. I then tag with the version number, roll a release package and install it on a pre production machine. Once the package is tested on a pre production machine I know that it will be ok in userspace -- if not I source the problem and roll a pre producton package again. HTH James On Apr 1, 2005 8:25 PM, Matthew Fonda wrote: > > Option [a] seems like the most logical thing to do, would probably work the > best. It might be nice to note on php.net somewhere right now before this is > fixed that PEAR will not install. > > > The options we have, as far as I can tell, are: > > > > [a] Re-release 5.0.4 with that file > > [b] Release 5.0.5 with that file (seems a bit too aggressive considering > > there are no code changes, and may cause confusion) > > [c] Instruct people to install PEAR from http://go-pear.org > > > > I lean towards option [a]. Thoughts? > > > > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >