Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43005
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.184 as permitted sender)
Message-ID: <00c301c98c7d$da9cce80$919f644d@foxbox>
To: "Hannes Magnusson" <hannes.magnusson@gmail.com>
Cc: "Lukas Kahwe Smith" <mls@pooteeweet.org>,
	"PHP Internals List" <internals@lists.php.net>
References: <53C9D049-8C10-48F2-8312-C8A81D2B5990@pooteeweet.org> <00a601c98c7b$4ed5a4a0$919f644d@foxbox> <7f3ed2c30902111113q364b4094q22c71c1046a984a6@mail.gmail.com>
Date: Wed, 11 Feb 2009 19:20:45 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 5.3 todos
From: steph@php.net ("Steph Fox")

Hi Hannes,

> Think about the online manual. In 2 years from now people should still
> be able to read the upgrading guide and it should still make sense
> without needing to hunt down random release announcements or outdated
> NEWS files.
>
> The upgrade which gets committed to php-src will be taken, word by
> word, and ported to Docbook and made available at
> http://php.net/migration53 (just like /migration52 and
> /migration51..).

But this was actually an add-on after I put the initial 5.1 upgrading guide 
together. A 200-line document became a 500-line document overnight, and 
voila - nobody reads the thing.

>> Is this entirely necessary? (I can see a case for listing new classes in 
>> the
>> global namespace.)
>
> Unless you want duplicated work, one file to php-src and one for the docs, 
> yes.

I'd like to know why you can't just take release info from the release notes 
for the manual. Duplicating the release notes seems a bit pointless.

- Steph

>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>