On Thu, 11 Jan 2001, John Levon wrote:
> That's good, but it should be left open. The reason is that 1.1.6 will
> have this bug. This will be the last stable release for a long
> time.
Why will it be the last stable release for a long time?
1.1.6 has taken far too long to get out the door and nearly everyone has
agreed we need to shorten our cycle again and get back to about 2-3 months
between releases (if not shorter).
Remember, Lars, posted the CVS HOWTO so we could all learn how we really
should be developing LyX: Major chunks in branches and merged once
stabilised. The HOWTO also showed how to keep branches synced up with the
trunk so your work is based on the current trunk and thereby makes merging
simpler. CVS trunk should nearly always be stable so we could almost have
a new release each time there's a commit to the trunk. "Almost" because
merged in major features are likely to be a tiny bit buggy or misfeatured
for the first week they are in.
Just because we are calling the next release 1.2.0 shouldn't get you
thinking in the Linux kernel way where major releases must be massively
different to the previous release (which is half the reason the kernel
release cycle is so long). Sure we are targetting having _all_ the
dialogs GUII for 1.2.0 but if Angus gets carried away with his controller
separation we'd be better of releasing 1.2.0 when we have half the dialogs
GUII.
Allan. (ARRae)
