Re: PHP 7 TODO list

On 15 May 2015 at 14:27, Maciej Sobaczewski <sobak@php.net> wrote: > Hello Peter, > > I should have some free time starting next Wednesday, so I will be happy > to help on the efforts. > Super! My first victim.. ahem, volunteer. > > There are few questions coming to my mind, though: > > - what about versions.xml - should we add "PHP 7" to almost every > function? (like we have "PHP 4, PHP 5" now) > Yes, we should do that. For functions that will be in PHP 7, anyway. > > - personally, I think it would be good to release new version of PhD with > the patch for marking functions as deprecated in versions.xml, however, I'm > not really sure if I can do this without a fuckup > If I can make a release of PhD, anyone can! I think it would be good for you to do it, just so the number of people with the know-how can increase. Hit myself and/or bjori on IRC if you'd like some hand-holding. > > - "Removed $is_dst parameter from mktime() and gmmktime()." - mentioning > this in the changelog is obvious, but what about the function prototype? > Leave or remove the parameter? > If this were any other release, we wouldn't hesitate to change the function prototype to the most up-to-date one. I don't see why this is any different. So long as all of the necessary changelog information is on the page, of course. > > I think that we should start with a skeleton for the migration guide. That > way, we should have clear reference about what has already been done. > Speaking of the migration guide, Adam (cc'd) have you done anything in this area yet? You've done a fantastic job in the past. > > Cheers, > Maciej. > > W dniu 2015-05-15 o 14:43, Peter Cowburn pisze: > >> Hi ladies and jellyspoons, >> >> So things are well under way with PHP 7 and internals has mostly sorted >> out what is going to be in there, it's time to get our little >> documentation hands dirty! >> >> To that end, I'm proposing to create, and maintain, a little effort to >> track what needs to be documented and for people to be able to "claim" >> items so that we can see what is being worked on and to prevent >> duplicating work unnecessarily. >> >> I figured that a wiki page, with a massive TODO list would be a good >> start. Rather than put it on wiki.php.net >> <http://wiki.php.net>, which >> restricts editing to @php.net <http://php.net> and >> "special" people, >> I've put up a wiki page on GitHub under the "gophp7" namespace (who are >> already doing excellent work with gophp7-ext for getting extensions >> shipshape) so that anyone [with a GitHub account] can get involved. >> >> https://github.com/gophp7/gophp7-docs/wiki/TODO >> >> Some work has been done already, starting to mention PHP 7 changes in >> the documentation (hero of the month: pasindu!) but there is a big pile >> still to do. >> >> Please share your thoughts, feelings, and kitten photos. >> >> Cheers, >> >> Peter >> >> P.S. Thoughts and ideas with regards to getting more non-phpdoc people >> involved with this would be super, too. I'd love to see some fresh faces >> getting involved with documentation, and we'll have lots of small, >> isolated documentation changes which are ideal for newcomers. >> > >