Hi Lukas, all,
'Scuse top-posting, no >>> history marks here.
It's not actually 'open' so much as 'under way' - the file's in place and
has content, it just needs some thought applying to it.
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...?
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 includes lists of all the
new functions and constants in the PHP global namespace.
Is this entirely necessary? (I can see a case for listing new classes in the
global namespace.)
For the same reason, I don't really see how it's relevant to mention new
core extensions (unless as replacements for previously existing core
extensions), new functions, stuff that is newly supported in Windows or new
features in PHP syntax (exception: reserved keywords). We should focus on
things that are deprecating, missing or else behave differently in some way
IMHO.
Comments welcome,
- Steph
----- Original Message -----
From: "Lukas Kahwe Smith" <m...@pooteeweet.org>
To: "PHP Internals List" <internals@lists.php.net>
Sent: Wednesday, February 11, 2009 5:07 PM
Subject: [PHP-DEV] 5.3 todos
Hi,
It seems aside from some smaller commits, the last minute closure
change has gone through without issues.
Our todo list however doesnt have that many checked off items:
http://wiki.php.net/todo/php53#next_release_beta2rc1
To me the biggest issue is the UPGRADING README. So please approach
Steph if you want to help.
The following items remain open:
- write UPGRADING README file (Steph)
- add more tests for fileinfo (Felix/Derick)
- make all extensions use php implementation of getenv (Pierre)
- reorganize the bundled php.ini files to production/development
recommendations (Eric/Nathan)
- re-enable phar for big endian systems (Scott)
The following remain open and it does not seem someone is actively
working in it:
- Fix static build of extension when static is the default and –enable-
snapshot-build is used
- Improve the build script to ease the parsing of the output and QA
- ob_flush() should fail to flush unerasable buffers
- tokenizer misses last single-line comment
- ob_start(): inconsistent behaviour with undefined callbacks
- pcntl_signal needs declare(ticks) which is deprecated since 5.3
- opendir() fails on Windows directories with parent directory
unaccessible
- Bus error during build of phar.php
- PDO: persistent connection leak
- memory leak in the re2c
- fix memleak in zend_object_handlers.c
- PHP_5_3 missed merge from PHP_5_2 for write_func callback
Other issues recently raised on the list
- reflection/arginfo overlap issue
- Throwing E_DEPRECATED on startup
- casting doubles to ints
I have send out an email to several larger OSS projects that are on
the primary-qa-te...@lists.php.net mailinglist. BTW: please subscribe
any key projects you know that are not yet on this list:
http://pooteeweet.org/blog/1439
Again, I will be offline 99% of the time starting this Saturday until
March 5th. I hope that while I am gone we will have another release
that covers the above mentioned issues and ideally that would be RC1
(unless bigger issues are uncovered that require larger changes).
Until then please let me know if you are taking over any of the above
items so that I can update the wiki. Speaking of wiki, Pierre also has
admin rights on the wiki and of course root access to the box.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
