Lukas Kahwe Smith wrote:
Hey Steph,
Personally I think we should list all changes. For certain changes we
should devote some explanations (like E_DEPRECATED). For the most part I
see this document as a place where we provide an overview of things
which then gives them the right key word to look in the documentation.
Also like in the case of E_DEPRECATED we should briefly explain the
reasoning and how people should adapt their php.ini files .. so in that
sense all longer text should be about migration issues, where are
documentation is more about documenting the behavior in each version.
I expect some people to skim this document, others to read it to the
letter, others will just grep it if they run into issues. Thinking about
it, we should somehow try and make sure that any likely error message
that people will see in their error logs after upgrading will get them a
hit when they search for it in this document.
So in summary, I feel the key point for this document is:
- a single document that lists all changes
- contains pointers that enables someone to look up more details in the
documentation
- enables people who get new "strange" error messages to find pointers
towards the documentation
- some lengthier migration related explanations that go beyond what we
want to provide in the documentation
That sounds about right ...
BUT perhaps some of the more complex explanations should have their own
document. If it 'requires more explanation than we want to provide in
the documentation' that does seem to suggest that a development perhaps
DOES need better doumentation?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
