Phil,
Based on past experience in dealing with primary testers we usually
only get responses when things go bad, as such waiting for positive
responses until rolling the final is not practical in my opinion. I
think the best I can propose is that we give testers at least one
week to try
Ilia Alshanetsky wrote:
Phil,
Based on past experience in dealing with primary testers we usually
only get responses when things go bad, as such waiting for positive
responses until rolling the final is not practical in my opinion. I
think the best I can propose is that we give testers at
Brian Moon wrote:
Phil Driscoll wrote:
Please add and/subtract to/from the above lists.
MediaWiki
[snip]
Those are the big in their space. We use MediaWiki daily in our company.
We're already testers.
Note that MediaWiki uses few (if any) $_POST arrays, so we encountered no
problems
On Wednesday 17 May 2006 17:59, Ilia Alshanetsky wrote:
Let's keep this number of lists to the minimum. Thanks to Lukas, we
already have a wiki with all this information, lets keep using it,
the release process is complex enough already without having to
scramble around looking for information
On Thu, 18 May 2006, Phil Driscoll wrote:
On Wednesday 17 May 2006 17:59, Ilia Alshanetsky wrote:
Let's keep this number of lists to the minimum. Thanks to Lukas, we
already have a wiki with all this information, lets keep using it,
the release process is complex enough already without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phil Driscoll wrote:
On Tuesday 16 May 2006 21:35, Richard Lynch wrote:
Would it be worth having a checklist of must-have software?
It's easy to see something big getting missed just because Joe is on
vacation or too busy to test, and everybody
Markus Fischer wrote:
Is there any software out there which uses PHPUnit(2)? So those
automatic suites could be used as well.
I have brought this up before. Sebastian Nohn has taken up this idea and
set up a box that checks out PHP from CVS, builds it, and then runs
make test as well as the
On 5/17/06, Sebastian Bergmann [EMAIL PROTECTED] wrote:
I have brought this up before. Sebastian Nohn has taken up this idea and
set up a box that checks out PHP from CVS, builds it, and then runs
make test as well as the unit tests of projects like PHPUnit and the
Zend Framework.
The big
Robin Ericsson wrote:
The big whohoo would be a complete PHPUnit test framework for PHP with
code coverage that replaces the old test framework.
As long as PHPUnit cannot run each test in a new PHP interpreter
process this would make no sense. And even then, why would we want to
replace
Lukas
To move this process forward, is there any chance that you could make a few
changes to http://oss.backendmedia.com/ReleaseChecklist?
First add an extra item to 'Getting the Release Candidate out there' saying:
Email [EMAIL PROTECTED] to notify the primary testers to get
testing. An
Jasper Bryant-Greene wrote:
I'm not necessarily suggesting that a release be delayed because *my*
application doesn't work, I'm just offering to test RCs against it and
report any bugs that it turns up. If the bug is found to be with PHP and
is sufficiently serious, then perhaps the release
Sebastian Bergmann wrote:
Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking them
to test their code against the release and let us know of any issues
that come up.
Sadly, this does not seem to work. Maybe because nobody from the
projects feels
Bonjour,
Greg Beaver wrote:
Sebastian Bergmann wrote:
Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking them
to test their code against the release and let us know of any issues
that come up.
Sadly, this does not seem to work. Maybe because nobody
Phil Driscoll wrote:
To move this process forward, is there any chance that you could make a few
changes to http://oss.backendmedia.com/ReleaseChecklist?
I have added a link to your post as a comment in the page. Since I am
not an RM I will leave it to Ilia and Derick to incorporate these
On Tue May 16, 2006 at 09:5439PM +0100, Phil Driscoll wrote:
I guess as well as a software list, we need an important platform list so we
know that an RC has been exercised on at least:
Linux X86 Apache module
Linux X86_64 Apache module
BSD Apache module
Solaris Apache module
Windows
OS X, preferably both on the Intel- and the PowerPC-platform.
Oh yes. I need to be able to develop on my MacBook Pro.
--
Brian Moon
-
http://dealnews.com/
Its good to be cheap =)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
On Wednesday 17 May 2006 16:47, Martin Jansen wrote:
OS X, preferably both on the Intel- and the PowerPC-platform.
added to
http://www.dialsolutions.com/phil/php/primarytesters.html
:)
--
Phil Driscoll
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
On Wed, 17 May 2006 17:19:06 +0100
[EMAIL PROTECTED] (Phil Driscoll) wrote:
On Wednesday 17 May 2006 16:47, Martin Jansen wrote:
OS X, preferably both on the Intel- and the PowerPC-platform.
added to
http://www.dialsolutions.com/phil/php/primarytesters.html
:)
Why don't you ask for an
Let's keep this number of lists to the minimum. Thanks to Lukas, we
already have a wiki with all this information, lets keep using it,
the release process is complex enough already without having to
scramble around looking for information on dozens of websites.
On 17-May-06, at 12:19 PM,
Ilia Alshanetsky wrote:
Let's keep this number of lists to the minimum. Thanks to Lukas, we
already have a wiki with all this information, lets keep using it, the
release process is complex enough already without having to scramble
around looking for information on dozens of websites.
Bonsoir
Pierre wrote:
Why don't you ask for an access to the wiki and update this list there?
-- Pierre
You need access to that ?
--
toggg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tuesday 16 May 2006 01:04, Lukas Smith wrote:
That being said .. if there are any additions people have to give better
guidelines for RM's please drop a comment at the following address:
http://oss.backendmedia.com/ReleaseChecklist
I've just added the following comment, which addresses part
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Phil Driscoll wrote:
On Tuesday 16 May 2006 01:04, Lukas Smith wrote:
That being said .. if there are any additions people have to give better
guidelines for RM's please drop a comment at the following address:
Hello Phil,
Tuesday, May 16, 2006, 9:07:13 AM, you wrote:
On Tuesday 16 May 2006 01:04, Lukas Smith wrote:
That being said .. if there are any additions people have to give better
guidelines for RM's please drop a comment at the following address:
http://oss.backendmedia.com/ReleaseChecklist
On Tuesday 16 May 2006 13:51, Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking
them to test their code against the release and let us know of any
issues that come up. If you want to be part of this group ask Lukas
to add you to the wiki page that can
Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking them
to test their code against the release and let us know of any issues
that come up.
Sadly, this does not seem to work. Maybe because nobody from the
projects feels responsible?
--
Sebastian
Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking them
to test their code against the release and let us know of any issues
that come up. If you want to be part of this group ask Lukas to add you
to the wiki page that can be found here:
On Tue, May 16, 2006 2:07 am, Phil Driscoll wrote:
On Tuesday 16 May 2006 01:04, Lukas Smith wrote:
That being said .. if there are any additions people have to give
better
guidelines for RM's please drop a comment at the following address:
http://oss.backendmedia.com/ReleaseChecklist
I've
On Tuesday 16 May 2006 21:35, Richard Lynch wrote:
Would it be worth having a checklist of must-have software?
It's easy to see something big getting missed just because Joe is on
vacation or too busy to test, and everybody knows Joe is gonna test
it...
Yes, so we need a list plus at least
On Tue, May 16, 2006 8:04 am, Sebastian Bergmann wrote:
Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking
them
to test their code against the release and let us know of any issues
that come up.
Sadly, this does not seem to work. Maybe because nobody
Phil Driscoll wrote:
Please add and/subtract to/from the above lists.
MediaWiki
Mambo/Joombla/Nuke
Those are the big in their space. We use MediaWiki daily in our company.
--
Brian Moon
-
http://dealnews.com/
Its good to be cheap =)
--
PHP Internals - PHP Runtime Development
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Richard Lynch wrote:
On Tue, May 16, 2006 2:12 am, Jasper Bryant-Greene wrote:
I like this idea. I can volunteer to do reasonably thorough testing
(both a 'make test' and real-world app testing) of 5.x releases on a
very large OO application
Hello,
okay, mistakes happen everyday but it really sucks that PHP.net
continues trying to hide mistakes.
1) PHP 5.1.4 was released with a nonsense announcement claiming that
there was only a problem with POST arrays or POST fileuploads.
- In reality a paid Zend developer had destroyed the
On 15-May-06, at 9:39 AM, Stefan Esser wrote:
Hello,
okay, mistakes happen everyday but it really sucks that PHP.net
continues trying to hide mistakes.
1) PHP 5.1.4 was released with a nonsense announcement claiming that
there was only a problem with POST arrays or POST fileuploads.
- In
Hey,
The code in the release did not change on bit, the only change was the
inclusion of the missing phar file, this hardly warrants 5.1.5 or even
5.1.4pl1. This will have no impact of people who have already
downloaded and installed PHP, nor will this impact people who have yet
to download
Ilia Alshanetsky wrote:
The code in the release did not change on bit, the only change was the
inclusion of the missing phar file, this hardly warrants 5.1.5 or even
5.1.4pl1. This will have no impact of people who have already downloaded
and installed PHP, nor will this impact people who have
Stefan,
Ironically
after that incident another Zend man came forward and dares to say I
don't trust our core testers anymore
He dared to say it because there's a QA mechanism in place that isn't
working - AKA a bunch of application developers testing Release Candidates
on their real-world
Stefan,
I don't see why this attack is directed at Zend people working on
PHP, where the release process is completely a community driven
effort (and last time I checked, no enterprise was involved in that
process either).
I agree the release process isn't perfect yet, and it becomes
On 15-May-06, at 11:50 AM, Stefan Esser wrote:
Hey,
The code in the release did not change on bit, the only change was
the
inclusion of the missing phar file, this hardly warrants 5.1.5 or
even
5.1.4pl1. This will have no impact of people who have already
downloaded and installed PHP,
Hello Andi,
I don't see why this attack is directed at Zend people working on PHP,
where the release process is completely a community driven effort (and
last time I checked, no enterprise was involved in that process either).
Well I don't see why Zend people commit code that obviously broke a
At 09:32 AM 5/15/2006, Stefan Esser wrote:
Hello Andi,
I don't see why this attack is directed at Zend people working on PHP,
where the release process is completely a community driven effort (and
last time I checked, no enterprise was involved in that process either).
Well I don't see why
-Original Message-
From: Stefan Esser [mailto:[EMAIL PROTECTED]
Sent: Monday, May 15, 2006 8:32 PM
To: Andi Gutmans
Cc: PHP internals
Subject: Re: [PHP-DEV] PHP Release Process Sucks
Hello Andi,
I don't see why this attack is directed at Zend people
working on PHP,
where
Hey Andi
My point was that this has nothing to do with Zend or not Zend.
My point is not that someone from Zend broke it, but that someone from
Zend blamed the community that THEY failed to find the problem. I
thought Zend is enough into PHP to test their own products against RC's,
too. It makes
Hello Dmitry,
It was my bug.
I am writing a lot of code for PHP and as result do some bugs.
I don't know a man who never does bugs.
Exactly. I (we) appreciate your work and the point was not that you
broke it. Like I replied to Andi, I also broke unserialize() in one of
the 4.3 releases in
On 15.05.2006 21:10, Stefan Esser wrote:
Hey Andi
My point was that this has nothing to do with Zend or not Zend.
My point is not that someone from Zend broke it, but that someone from
Zend blamed the community that THEY failed to find the problem. I
thought Zend is enough into PHP to test
On 15.05.2006 21:17, Stefan Esser wrote:
Hello Dmitry,
It was my bug.
I am writing a lot of code for PHP and as result do some bugs.
I don't know a man who never does bugs.
Exactly. I (we) appreciate your work and the point was not that you
broke it. Like I replied to Andi, I also broke
Antony Dovgal wrote:
So it makes me a bit angry when someone who did nothing (except for a
couple of mails to internals@) for PHP since December starts treating me
and Dmitry (who's one of the most active PHP contributors) like a
millionaires who earned their millions from poor PHP community.
So it makes me a bit angry when someone who did nothing (except for a
couple of mails to internals@) for PHP since December starts treating
me and Dmitry (who's one of the most active PHP contributors) like a
millionaires who earned their millions from poor PHP community.
Tony, you have
Sebastian Bergmann wrote:
Now this is an unfair argument as Stefan cannot (for whatever reasons)
commit his work to cvs.php.net.
Strike that, I was educated about this on IRC just now. My initial
point is still valid to some degree, IMHO: just because Stefan's work
does not go into
Stefan,
If anything, that was a good drill on why it's not a good idea to
write sarcastic, negative emails to people. Unless of course, your
aim is to annoy them into starting a heated threads. You've raised
some good points in your original email, and it's a shame you diluted
your message
Sebastian Bergmann wrote:
Now this is an unfair argument as Stefan cannot (for whatever reasons)
commit his work to cvs.php.net.
Strike that, I was educated about this on IRC just now. My initial
point is still valid to some degree, IMHO: just because Stefan's work
does not go into cvs.php.net
Zeev,
Instead of discussing the points, we're discussing these pointless
topics of who contributes more. I suggest we stop here, I think it's
absurd to question the level of contribution from any of you three.
You are right. The discussion can stop here. Antony once again proved
every single
Hello Stefan,
Monday, May 15, 2006, 6:32:25 PM, you wrote:
Hello Andi,
I don't see why this attack is directed at Zend people working on PHP,
where the release process is completely a community driven effort (and
last time I checked, no enterprise was involved in that process either).
Well
At 21:29 15/05/2006, Stefan Esser wrote:
Zeev,
Instead of discussing the points, we're discussing these pointless
topics of who contributes more. I suggest we stop here, I think it's
absurd to question the level of contribution from any of you three.
You are right. The discussion can stop
Marcus Boerger wrote:
To rephrase Andi So people screw up. I prefer having the occasional
screw up then less people helping out. We are a community [...]
What we need is more helping hands and less comlaining notes. Actually
we are constantly working on increasing or QA efforts. And from my
55 matches
Mail list logo
