Hi,

> I'd like to raise the option of releasing 4.2.3 again.  I believe that it
> would be quite a while before 4.3.0 is out, and there are quite a
> few fixes
> in the 4.2 branch that should make the userbase as soon as possible,
> especially the Windows userbase.
> I think that releasing 4.2.3 can be done within approximately one week,
> with one RC, barring unexpected surprises.
> Opinions?

As I already said some weeks ago, 4.2.3 would be great if these Bugs were
fixed in 4.2.3:

http://bugs.php.net/bug.php?id=18639
http://bugs.php.net/bug.php?id=18623
http://bugs.php.net/bug.php?id=18228
http://bugs.php.net/bug.php?id=17449

So, as you can see from this and some other Bugs PHP is on most
64Bit-Platforms buggy as hell. Most things seem to bei fixed in 4.3.0-dev
right now and I don't know, how difficult it is to port them back to 4.2

I don't know if http://bugs.php.net/bug.php?id=18640 appears just because
I'm dumb or anything (it works with 4.2.0, but I normally don't install PHP
on that machine as I'm a programmer not an admin ;)). Maybe Thies knows if I
just forgot some exports or options and can close this bug.

Here I request again to use my scripts (latest downloadload
http://php.nohn.net/autotest/php4-test.1.43.2.tar.gz) for the regression
tests as the ones currently in php-qa cvs require to install perl and
blablabla. There is still a bug in md5file-testcase (it's the testcase that
does'nt work) and it's still dirty coded. See
http://php.nohn.net/autotest-stats.php and
http://php.nohn.net/autotest-submit.php for how a webpage to this could look
like. If you don't like my scripts say it, I don't want to be too much
Manuel Lemosish ;) but so far I never got any answer, neither postive nor
negative.

Regards,
   Sebastian Nohn
--
+49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/
PGP Key Available - Did I help you? Consider a gift:
http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to