RE: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-29 Thread Sebastian Nohn
Hi, > Aren't most of your problems related to using a 64-bit platform? Where > were you during QA on 4.2? My sort() stuff works just fine here. On another place in that group where I had very little to do with PHP and if I had to do with it, it was Windows or Linux on x86... Regards, Seba

Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1?

2002-07-28 Thread Rasmus Lerdorf
Aren't most of your problems related to using a 64-bit platform? Where were you during QA on 4.2? My sort() stuff works just fine here. -Rasmus On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Hi, > > > there are not enough people for this. > > Well. As I already said: Then there are'nt enough pe

Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread Melvyn Sopacua
At 20:44 28-7-2002, [EMAIL PROTECTED] wrote: > > Well. As I already said: Then there are'nt enough people for 4.3.0 too. Yes > > I know, you are the maintainer of 4.2.x, Stig is the maintainer of 4.3.0. > >There are not enough people to do two releases at one time. Actually - one issue there, ar

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread James Cox
> Following that, why not do what a number of people do, and do > > major.minor.patch > > major releases say every 6 months > minor ones every 2 - unless serious patch required > patches as required > > This allows people to predict the times also. > i would see this working, given it's what we do

Re: [PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1?

2002-07-28 Thread derick
On Sun, 28 Jul 2002, Sebastian Nohn wrote: > Hi, > > > there are not enough people for this. > > Well. As I already said: Then there are'nt enough people for 4.3.0 too. Yes > I know, you are the maintainer of 4.2.x, Stig is the maintainer of 4.3.0. There are not enough people to do two release

[PHP-DEV] Re: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread derick
On Sun, 28 Jul 2002, Sebastian Nohn wrote: > That is no solution for the real problem. People are frustrated because they > don't know if their software runs on the next machine they put it on because > this machine maybe has another PHP-version. It's the same thing like GD or > Apache 2. Why was

[PHP-DEV] RE: [PHP-QA] Re: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread Sebastian Nohn
Hi, > there are not enough people for this. Well. As I already said: Then there are'nt enough people for 4.3.0 too. Yes I know, you are the maintainer of 4.2.x, Stig is the maintainer of 4.3.0. Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Ava

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread Melvyn Sopacua
At 19:40 28-7-2002, Liz wrote: >Following that, why not do what a number of people do, and do > >major.minor.patch Basically that's how it is, but the understanding of major and minor is a little outof sync with other packages out there or QA of minors isn't wat is should be, which ever you pre

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread Liz
Following that, why not do what a number of people do, and do major.minor.patch major releases say every 6 months minor ones every 2 - unless serious patch required patches as required This allows people to predict the times also. -- PHP Development Mailing List To uns

[PHP-DEV] RE: [PHP-QA] RE: [PHP-DEV] RE: [PHP-QA] PHP 4.2.3RC1 ?

2002-07-28 Thread James Cox
the large amount of time between the branches. > > Yes. That may be. But there are a lot of bugfixes in the latest > STABLE-snapshot I tested (26/07/02) - or exactly: All bugs I experienced > were fixed. So the easiest thing would be to cancel all new features that > were planned for 4.2.3 and mo