On Thu, 3 May 2007, José Matos wrote:
I am sorry, I can't parse this sentence. :-)
Here's what I actually meant:
I don't think that's a good idea, as we _would_then_ expect the
file format to change between the rc and the stable release.
So I think a RC would be bad when we _expect_ the file format to change.
IMO, it is all a matter of timings, ...
I agree it's partly about timing, and irrelevant in practice as Bo seems
to be close to done.
However (and I apologize for going all semantic on you:-), but according
to the "definitions" I got from you (José), I've understood it as follows:
http://wiki.lyx.org/Devel/UnsortedNotes#toc3
Beta release
A beta release is a release of the LyX software from the
development source code at a point when very few (and minor) new
features are expected to be added before the first stable release.
Release candidate (prerelease)
A release candiate is a release of the LyX software from the
development source code at a point when only bug fixes are
expected to be added before the first stable release.
Hence, without Bo's feature it should be a beta release. With it, and
expecting no other features, we should do a release candidate.
Do we know of any bugs that should be fixed before 1.5.0 that require a
change in the file format?
Do we know of any "must have now" features that require a file format
change?
If the answer is no the questions above, I suggest we let Bo's thing into
the bull pen and then publish it as a release candidate. Since it's a
release candidate, no more new features are to be added Until 1.5.0 has
been released.
/Christian
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
