[PHP-DEV] PHP in 2003 (leading to PHP 5)

2003-01-01 Thread Wez Furlong
I hope you all had a joyous night last night and that it forms that start of a great New Year! Now, let's get our heads straight on what we are doing for 2003 :) You may remember (especially if you read Derick's Look Back) that I said something about building against ZE2 by default once we

[PHP-DEV] CVS mangled (netware/apachecore.imp, netware/bisonflexzend.bat)

2003-01-01 Thread Wez Furlong
% cvs -q up cvs server: nothing known about netware/apachecore.imp cvs server: nothing known about netware/bisonflexzend.bat I can't find any trace of these files in my checkout (or in the CVS files), so I presume that something has been munched on the server side? --Wez. -- PHP Development

[PHP-DEV] ChangeLog

2003-01-01 Thread Wez Furlong
Is there some magic that needs to be done to rotate the ChangeLog? By this I mean: gzip ChangeLog mv ChangeLog.gz ChangeLog2002.gz touch ChangeLog cvs add -kb ChangeLog2002.gz cvs ci -m rotate changelog ChangeLog ChangeLog2002.gz It seems the most recent entry in the log is from the 29th

[PHP-DEV] CVS Account Request: mcilvena

2003-01-01 Thread Troy Mcilvena
I'm interested to helping to maintain php.net, and contribute my work in the area of content and design management. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Win32 build broken

2003-01-01 Thread Sebastian Bergmann
basic_functions.obj: error LNK2001: Unresolved external symbol: _zif_stream_register_filter basic_functions.obj: error LNK2001: Unresolved external symbol: _zm_startup_user_filters -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/

Re: [PHP-DEV] PHP in 2003 (leading to PHP 5)

2003-01-01 Thread Brad LaFountain
3. Bundle PHP-Soap (and stop the bleeding of PHP users) I know I've been saying for a while now that I'm going to start working on this again but I have yet to do it. I do plan to work on this again. I would like to see it bundled with php5 but it defintly needs some work. If its possible I

Re: [PHP-DEV] CVS mangled (netware/apachecore.imp,netware/bisonflexzend.bat)

2003-01-01 Thread James Cox
On Wed, 2003-01-01 at 08:17, Wez Furlong wrote: % cvs -q up cvs server: nothing known about netware/apachecore.imp cvs server: nothing known about netware/bisonflexzend.bat I can't find any trace of these files in my checkout (or in the CVS files), so I presume that something has been

Re: [PHP-DEV] ChangeLog

2003-01-01 Thread James Cox
On Wed, 2003-01-01 at 08:21, Wez Furlong wrote: Is there some magic that needs to be done to rotate the ChangeLog? By this I mean: gzip ChangeLog mv ChangeLog.gz ChangeLog2002.gz touch ChangeLog cvs add -kb ChangeLog2002.gz cvs ci -m rotate changelog ChangeLog ChangeLog2002.gz It seems

Re: [PHP-DEV] PHP in 2003 (leading to PHP 5)

2003-01-01 Thread Shane Caraveo
Roadmap: 1. Switch to ZE2 by default 2. Establish PECL CA authority and binary package/release process (particularly important for win32) 3. Bundle PHP-Soap (and stop the bleeding of PHP users) 3a. Collect underpants 4. ? 5. Profit #3 doesn't belong in a general roadmap. What does

Re: [PHP-DEV] PHP in 2003 (leading to PHP 5)

2003-01-01 Thread Steph
With this also extensions now can take on a life of their own, releasing at different times than php, and visaverse. I think this would make releasing new versions of php much more manageable. Do you? Not every extension has a named maintainer .. Shane - Steph -- PHP Development

Re: [PHP-DEV] PHP in 2003 (leading to PHP 5)

2003-01-01 Thread George Schlossnagle
I think this would make releasing new versions of php much more manageable. Do you? Not every extension has a named maintainer .. At worst, the maintenance would be as it is now. Or is the worry that some extensions will go unmaintained if they are moved into PECL? My take on that would

Re: [PHP-DEV] PHP in 2003 (leading to PHP 5)

2003-01-01 Thread Steph
I think this would make releasing new versions of php much more manageable. Do you? Not every extension has a named maintainer .. At worst, the maintenance would be as it is now. Or is the worry that some extensions will go unmaintained if they are moved into PECL? My take on that