Andre Poenitz <[EMAIL PROTECTED]> writes:
| I think we need some automatism to solve the dead-lock issue. Like "if pre1
| is not out after a four week freeze, the freeze is revoked"...
Yes, but in what way does that help?
Let's say that we are in review state instead: No patches go into cvs
unless it has been reviewed by at least one "core" developer. Call it
"slush" state if you want to.
And I am not sure about who should be in the "core" group.
| Hanging
| around indefinitely does not help anybody, neither the project nor the
| users. It's pretty irrelevant from a user's point of view whether he does
| not get an update because of an overly long freeze or because of on-going
| development without official releases. But in the latter case he gets at
| least the chance of an improvement...
I agree.
But the objective is not to cram as many features as possible into the
next release, but to get the next release out of the door. The best
would be for all of us to look at what needs to be done and help
doing it, even if it means fiddling with code that is not "our own".
I know that I am not good at that, mostly because I am a bit daunted
by the the whole guii, and the task of learning qt.
--
Lgb
