Michael Gerz <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| >I would really like to avoid this patch for 1.4.0. Is it really
| >critical?
| >
| Lars, I don't understand your policy. What's the benefit of postponing
| a bug fix until 1.4.1? In which way does it increase LyX's stability?
By continue to work on "stuff" for 1.4 you effectively make 1.4.0
never happen. (not this patch though, it seems to fix a real problem
and also to be a regressions from 1.3.x)
| OTOH, the patch provider is annoyed because his fix is not applied;
| the users are annoyed because they run into a problem for which there
| is already a solution; and the LyX developers (beside you :-)) are
| annoyed because they have to maintain a new bugzilla entry and have to
| apply the fix (after some rework) twice to the stable branch and to
| the head.
|
| IMHO if a patch fixes a bug, it should go in as soon as possible.
No. Not when it is not a reported/critical bug (at this stage in
development) . Then it just help delaying 1.4.0 even further.
At this stage in the release process I don't want _any_ patches that
don't fix real (reported) problem, blatant bugs or severe regressions
from 1.3.x
Do you want 1.4.0 released or not?
--
Lgb
