[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

> As I said, I don't think it's a big deal, but I think it will only have > slight negative impact, and even slighter positive impact. I believe that > people who are willing to download RC's and test them as such (i.e., send > detailed and informative bug reports, or even positive summaries) wou

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

The question is, if you think people will actually download the RC in order to test it (as opposed to using it) - why won't they join the QA team? At 17:11 2/5/2001, Sascha Schumann wrote: > > As I said, I don't think it's a big deal, but I think it will only have > > slight negative impact, an

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

At 05:15 PM 5/2/2001 +0300, Zeev Suraski wrote: >The question is, if you think people will actually download the RC in >order to test it (as opposed to using it) - why won't they join the QA team? Because they can't really be bothered with being part of the QA team and seeing all the Emails. Bu

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

On Wed, 2 May 2001, Zeev Suraski wrote: > The question is, if you think people will actually download the RC in order > to test it (as opposed to using it) - why won't they join the QA team? Their job description might list "test new software releases before putting them into production,

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

At 17:29 2/5/2001, Sascha Schumann wrote: >On Wed, 2 May 2001, Zeev Suraski wrote: > > > The question is, if you think people will actually download the RC in order > > to test it (as opposed to using it) - why won't they join the QA team? > > Their job description might list "test new softwar

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

> > Their job description might list "test new software releases > > before putting them into production," and not "join the PHP > > QA team." > > "Testing new software releases before putting them into production" is > pretty much a one sentence description of what 'Quality Assurance'

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

At 05:34 PM 5/2/2001 +0300, Zeev Suraski wrote: >I don't seem to recall Linux publishing far-reaching announcements about >-pre versions. If you walked around the development mailing lists or the >behind-the-scene web sites, you could hear about it, much like you can >with PHP today. Linux k

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

Okay guys, do whatever you want. Most people seem to agree with you. Zeev At 17:42 2/5/2001, Andi Gutmans wrote: >At 05:34 PM 5/2/2001 +0300, Zeev Suraski wrote: > >>I don't seem to recall Linux publishing far-reaching announcements about >>-pre versions. If you walked around the development

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

At 05:48 PM 5/2/2001 +0300, Zeev Suraski wrote: >Okay guys, do whatever you want. Most people seem to agree with you. At least you'll be able to give us the "I told you so" speech if it makes things worse :) Andi -- PHP Development Mailing List To unsubscribe, e-mail:

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

Zeev Suraski wrote: > "Testing new software releases before putting them into production" is > pretty much a one sentence description of what 'Quality Assurance' is. that's QA for their products usually and not so much for 3rd party components > I don't seem to recall Linux publishing far-reach

[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

> The question is, if you think people will actually download the RC in order > to test it (as opposed to using it) - why won't they join the QA team? Because they have enough time to make sure their software still works with the RC, but not enough time to wade through all the QA emails. :-) Mos

Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

On Wed, 2 May 2001, Zeev Suraski wrote: > At 17:29 2/5/2001, Sascha Schumann wrote: > >On Wed, 2 May 2001, Zeev Suraski wrote: > > > > Their job description might list "test new software releases > > before putting them into production," and not "join the PHP > > QA team." > > "Testin

Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] 4.0.6 (fwd)

> I would rather describe QA as "Making sure the release does have as least > bugs as possible". IMO this is different then just testing RC's. I think a > QA team should be the team who says "Yes, release it" or "No, there are > still some bugs left we want to fix". Of course, in order to do this,