include it in a 5.4 if that is the
version name for the next release.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
the hell out of everyone.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 12.03.2010, at 14:52, Jani Taskinen wrote:
On 03/12/2010 03:43 PM, Lukas Kahwe Smith wrote:
Because no decision has been made. Jani is creating facts without
basis. Furthermore normal development is continuing on the branches
we decided to have. Now there is suddenly a 5.4. The point
On 12.03.2010, at 15:27, Andrey Hristov wrote:
Lukas,
Lukas Kahwe Smith wrote:
On 12.03.2010, at 14:52, Jani Taskinen wrote:
On 03/12/2010 03:43 PM, Lukas Kahwe Smith wrote:
Because no decision has been made. Jani is creating facts without
basis. Furthermore normal development
,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
to be..some PHP 3 thing?
Good point. We should probably remove it before 5.3.1
You mean marking it deprecated and removing it in PHP 6.0?
Seems sensible to me.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net
On 02.07.2009, at 14:48, Derick Rethans wrote:
On Thu, 2 Jul 2009, Lukas Kahwe Smith wrote:
On 30.06.2009, at 11:57, Hannes Magnusson wrote:
On Tue, Jun 30, 2009 at 11:15, Jani Taskinenjani.taski...@sci.fi
wrote:
Hannes Magnusson wrote:
bjori Tue Jun 30 08:49:05 2009 UTC
need to be merged to HEAD?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
;
}
}
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net
On 19.06.2009, at 10:50, Lukas Kahwe Smith wrote:
Hello!
we have packaged PHP 5.3.0RC4, which you can find here:
http://downloads.php.net/johannes/
Windows binaries are available here:
http://windows.php.net/qa/
This this release candidate focused on bug fixes and stability
improvements
of the 21st without any further changes so we can test the
packages. In case something critical, unexpected, pops up please
notify us asap.
June 25th 2009
Release PHP 5.3.0 final.
We are still on track for this one.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List
obvious mistakes at time and its just really ver
inconvenient if we have such stuff during the final build testing
right before an RC.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
build testing and fixing done if we constantly have
commits for bug fixes going on.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
into 5.3.1.
Again a commit freeze means no commits to any part unless its clearly
a build fix or just touches README's. When in doubt ask Johannes (who
should be available again some time tonight).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net
and design choices.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
* 3) is
flawed anyway
with the old (err, formerly new) double-long conversion method,
but that
could be changed to get the same result cross-platform...
Sounds like we have a BC issue?
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List (http://www.php.net
On 28.04.2009, at 12:51, Lukas Kahwe Smith wrote:
Aloha,
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting
Monday evening. Also with RC2 any feature additions, regardless of
how small, will no longer
. Please keep track of any HEAD commits that need merging or let
me know about them so I can keep track of them (dunno if it makes
sense to just write a note in the HEAD commit that this changes needs
merging into 5_3).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP CVS Mailing List
On 20.03.2009, at 12:37, Ferenc Kovacs wrote:
On Fri, Mar 20, 2009 at 12:01 PM, Lukas Kahwe Smith m...@pooteeweet.org
wrote:
Hello,
We are not in a commit freeze on the 5_3 branch. For today for any
commit
not just affecting README's (as in anything affecting buolding or
build
testing
the key count -1
instead
+ of the key count). (David C.)
only one NEWS file entry per change .. as in the earliest branch that
will get released with the change.
i have recently updated the README on this point:
http://php.net/reST/php-src/README.CVS-RULES
regards,
Lukas Kahwe Smith
[EMAIL
just committed an update to the above document (should show up in an
hour or two on that site) that clarifies some of the issues you have
run into. Latest version is of course always available in HEAD CVS.
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http
On 09.11.2008, at 16:16, Jani Taskinen wrote:
Why not MFH to the stable branch too? a.k.a. PHP_5_2..
in the past i have been told to not MFH these kinds of README changes
to maintenance branches.
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http
On 04.09.2008, at 16:26, Lukas Kahwe Smith wrote:
Summary:
- So lesson learned from my side (and thanks to the readme for
future RMs as well).
- Pierre will handle creation of a libming 0.3 compatible ext/ming
PECL release
- ext/fbsql history can probably be saved
- ext/fdf and ext/sybase
not be in pecl
- ext/ncurses has been moved a while ago and all is well
- ext/dbase history is not going to be available via cvs.php.net/pecl
unless someone is willing to put in the time
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe
or not.
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 31.08.2008, at 12:11, Pierre Joye wrote:
Hi Hannes, Lukas.
On Sun, Aug 31, 2008 at 12:05 PM, Lukas Kahwe Smith [EMAIL PROTECTED]
wrote:
Sounds sensible. Anyways, I would appreciate it if someone who
knows would
write a howto, so that RMs can verify that things are done
properly. I
).
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
in
maintaining it :)
I was just going to propose you :)
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
);
}
Best regards,
Marcus
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 06.08.2008, at 21:37, Stanislav Malyshev wrote:
Hi!
+General notes and tipps
I think you have a typpo here ;)
Bah, why does english have to be different than german? :)
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe
it?
regards,
Derick
still not MFH'ed .. or?
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 21.07.2008, at 15:19, Jani Taskinen wrote:
I don't know who invented MFB..
I guess it's its a last resort attempt to save a bunny when you
screwed up with a commit .. therefore it should be called SAB (saving
a bunny).
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP CVS
On 01.02.2008, at 23:05, Pierre Joye wrote:
2008/2/1 Marcus Boerger [EMAIL PROTECTED]:
Crosspost, hopefully silencing this issue for 5.*
AND 6 will have an E_WARNING or even an E_ERROR on this.
What are the gains?
What are the real reasons behing strictness? I really get annoying by
On Dec 27, 2007, at 2:44 PM, Hannes Magnusson wrote:
On Dec 27, 2007 2:10 PM, Dmitry Stogov [EMAIL PROTECTED] wrote:
dmitry Thu Dec 27 13:10:20 2007 UTC
Added files: (Branch: PHP_5_3)
/php-src/ext/soap/tests server030.phpt server030.wsdl
Modified files:
On 16.11.2007, at 14:21, Ilia Alshanetsky wrote:
I don't see why PDO should follow oracle's rules for generic
functionality. I think current implementation is good as is.
1) its a BC break that can affect any user
2) this can break queries for Oracle users porting to PDO in a very
non
On 22.11.2007, at 23:11, Johannes Schlüter wrote:
Lukas,
once again: Thanks for your work!
A small comment below:
On Thu, 2007-11-22 at 18:12 +, Lukas Smith wrote:
+ PHP_5_2 Is used to release the PHP 5.2.x series. Only minor
feature
+ enhancements may go in here, but please
On 01.11.2007, at 00:56, Lorenzo Alberton wrote:
Lukas Kahwe Smith wrote:
I talked to Christopher Jones (of Oracle fame) and Lorenzo (MDB2
maintainer). Its clear that the only named parameter supporting
database I know does not support dash inside named parameters. Its
also dangerous
On 30.10.2007, at 12:00, Johannes Schlüter wrote:
Ilia,
I don't think this is right. SQL operators shouldn't be part of a
parameter name imo.
I talked to Christopher Jones (of Oracle fame) and Lorenzo (MDB2
maintainer). Its clear that the only named parameter supporting
database I know
Johannes Schlüter wrote:
Dmitry Stogov wrote:
Yes, of course. I'll update it soon.
I am going to backport several other patches nearest days, so I'm not sure
if I should update version every day.
It should be enough to change it once before an release. People running
snapshots should expect
Ilia Alshanetsky wrote:
iliaa Sun Apr 15 16:50:42 2007 UTC
Modified files: (Branch: PHP_5_2)
/php-src NEWS
/php-src/ext/pdo_mysql mysql_statement.c
Log:
Fixed bug #40935 (pdo_mysql does not raise an exception on empty
fetchAll()).
Why should there be
Dmitry Stogov wrote:
dmitry Fri Apr 7 13:45:23 2006 UTC
Modified files: (Branch: PHP_5_1)
/php-src/sapi/cgi cgi_main.c
Log:
CGI anf FastCGI assume $_SERVER and $_ENV have the same values,
so we don't need construct the same arrays twich and may just copy it
Marcus Boerger wrote:
helly Thu Mar 30 17:37:50 2006 UTC
Modified files: (Branch: PHP_5_1)
/php-src/ext/xmlreader php_xmlreader.c
Log:
- MFH Return NULL instead of '' if node does not exist
dont you think this could cause issues for people .. maybe wait for
Yasuo Ohgaki wrote:
yohgaki Mon Mar 27 02:59:55 2006 UTC
Modified files: (Branch: PHP_5_1)
/php-src/ext/pgsql pgsql.c
Log:
remove pg_execute() E_WARNING error when query plan is not defined
Sorry but I do not understand the logic behind this change. Nor do I
hi,
furthermore are you aware that there are several fixes that are also not
applied to 5.0.x (atleast I know for sure that several streams fixes
fall into this category). I really dont see the point in doing more
5.0.x releases if they dont fix countless bugs that are marked as fixed
in
44 matches
Mail list logo
