If I had the same amount of time to spend to work on LyX I had in June I'd be pretty disappointed by the current speed of the development process. Fortunately I have not.
Nevertheless I think we need to adjust the process in the future somehow. The 1.2 and 1.3 freezes somehow follow the same scheme: Something that was considered "necessary" for the release was not finished and nobody really helped out. This basically means we waste a potential of several "volunteer months" worth of work - and there is no "auto-correction" mechanism that breaks the dead-lock which occurs "if nobody does anything" I have no strong opinion or even an idea on how to solve that, I just want to say that there _is_ a problem. A serious one to be precise. Making people help out would probably the way to go if this were a company. But forcing something down the throat of volunteers may work once or twice, but that's not sustainable over years. 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"... 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... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
