Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43015
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain analysisandsolutions.com from 166.84.1.72 cause and error)
Date: Wed, 11 Feb 2009 22:29:14 -0500
To: PHP Internals List <internals@lists.php.net>
Message-ID: <20090212032914.GA5060@panix.com>
References: <53C9D049-8C10-48F2-8312-C8A81D2B5990@pooteeweet.org> <00a601c98c7b$4ed5a4a0$919f644d@foxbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00a601c98c7b$4ed5a4a0$919f644d@foxbox>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [PHP-DEV] 5.3 todos
From: danielc@analysisandsolutions.com (Daniel Convissor)

Hi Steph:

On Wed, Feb 11, 2009 at 07:02:35PM -0000, Steph Fox wrote:
>
> In the last two upgrading guides, we've repeated much of what is already 
> in the NEWS file or in the release notes. This makes me wonder what the 
> point is of having an upgrading guide...?

Because the guide is in the manual.  The manual is the difinitive source 
on how to use PHP.


> The initial idea was to have some way to tell users in general (and  
> sysadmins in particular) which existing code might break in the new PHP  
> version, and how to work around those issues. It should be a relatively  
> short file if we stick with this, but what we actually have (now and for 
> the last two releases) is 500-plus lines of text that ...

Sure, the guide be better structured.  But it should contain everything.

Thanks,

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409