Jani wrote:
> <CRAZY IDEA>
> Maybe we should have something like the terrorist cells?
> ie. groups of 3 persons who know only about the one above them?
>
> X
> __|_
> / \
> a b
> / | \ / \
> c (d) e e g
>
[...]
> </CRAZY IDEA>
Wow.... this sounds like one of my ideas Jani. :)
All we need now are some phpqat_tree_balance, phpqat_tree_...
functions and we are good to go! ;)
Seriously, IMO, this would be something fun to test off list
in one of the lags between a RC. We might learn something
neat and we might come up with a bunch of useless but
wickedly funny TLAs. :)
> >>4.0.5 took very long to release, and it seems like it could
> >>have been released a month ago - pl1 is inevitable anyway.
> >I don't see a pl1 happening. We will go right to 4.0.6.
>
> Why would we need a pl? As there really isn't anything that
> broken which would need it? (nothing that broken that wasn't
> broken before)
>
> >I don't think that the QA team is a joke just because they can't
> >necessarily pull the plug on a release. Don't forget that a lot of the QA
>
> Yes it is. As long as there is less than 5 persons who can decide
> on this, QA is a joke.
>
> >Anyway, why are we continuing to waste time on this instead of fixing
bugs
> >and emptying the bugs database.
>
> At last he gets to the point! :)
After taking the time to really think about the current state
of the QA process, I think that we are doing just fine.
Our current process is better than the old process (aka none)
Now, each of us is smart enough to be able to single-handedly
rework the process into a perfect shining vision of how
QA should run. ;) However, as a group, we have to be
moderate - or perhaps to rephrase that, we can't ramrod
changes past Zeev. ;)
Those of us who want to improve the process can do so by
watching the areas that matter to us.
I want to keep unneeded changes out of the RC process.
My opinion on RCs is like my mother's opinion on dinner:
Don't heap up your plate so much, you can always
go back for seconds.
So, I should watch CVS and squeal when anything non
bug related comes down the pipe.
If I do this regularly, I would guess that I would
have a much greater effect than any written set
of strict guidelines.
I think that if each of us takes a healthy interest
in the areas that matter to us and works to help
handle the relevant part of the process, we will find
that the process smooths out.
Take a look at who has made the most difference in how
we do things - it is not the people who make policies
for other people to follow. It is the people who do
the work and in doing so, establish how others should
do it.
--zak
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
