The lucene indexing is almost ready. (I'm looking for a solution for large modifications which require a lot of reindexing, but thats not a new feature).

I plan to restructure the "computed property" computing mechanics to allow userdefined computed properties (e.g. inherited properties).

I have a first version for automated testsuite runs that allow to test a number of configurations automatically. I plan to check in this ASAP.

Two testcases regarding locks are currently failing.

Nevertheless, I would welcome a shorter release cycle, so from my side there is no stopper for a next release. The second point can wait until 2.3.

Regards, Stefan


Oliver Zeigermann wrote:

Folks,

I am a bit concerned about the duration of our release cycles. E.g.
some contributions in 2.1 are much older than half a year before they
are even released as stable.

Apache rule is to release early and often.

My proposal is to speed up the cycle for 2.2 and subsequent releases
and put less new stuff into each of them. My impression is that 2.2
almost has got enough new features to justify a new release.

What do you think? What do you want to add and when? What is in your
pipeline for 2.2? Mine is empty...

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-- Stefan L�tzkendorf -- [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to