Wolfgang Jeltsch wrote:
Am Dienstag, 3. April 2007 21:39 schrieb Bob Harner:
Wolfgang, as a user of Lenya 1.2.4 for almost 2 years now, I wouldn't
recommend that anyone start a new project with that old and buggy code
at this point. The 1.2.5 version is probably a little better (but I
haven't tried it).
As an outside observer, Lenya 1.4 seems pretty close to me (a very
small number of weeks?). A release candidate was proposed recently,
which is a good sign. Yes, it has taken a very long time, but many
open source projects take years to produce major new versions. Don't
bet your job on it being released by any particular date, but if you
don't need to make a decision right away, 1.4 may be worth the wait.
There are some very cool architectural changes in it, and major
improvements throughout. Meanwhile you can download the unreleased
1.4 trunk from SVN and give it a try -- always a good idea when
valuating any open source product.
Thanks a lot for these clarifications.
Well, I have to install some CMS during the next weeks. And I don’t want to
wait for an indefinite amount of time which might be several months at the
end. (Yes, I have experience with waiting for Debian releases…) So if 1.4
cannot be used now or at least withing two weeks or so, it’s not for me. Can
1.4 already be used for production (whereby some small problems wouldn’t
matter)?
Best wishes,
Wolfgang
I have began deploying 1.4 in a beta environment. Still need to work up
quite a bit of documentation for it and a stable release is highly
desired. Most of what my users have found are more polish issues.
However, we're using FCKeditor, so I don't know how the rest of the
editors are functioning at this moment. However, I am also running
several patches I haven't put up on bugzilla yet to achieve this. We
have a demo in two weeks and I feel quite confident about it. However, I
am very carefully watching each commit coming in to the 1.4 svn tree.
The devs are waiting for one change to be applied before doing the RC.
It sounds like this may be a month or so before the changes can be
applied. I would say the current svn trunk is usable in its current
state, minus some polish. However, there hasn't been a formal code
freeze so I am afraid that could change at any moment.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
