Hi,
I really would like to see getting
http://framework.zend.com/issues/browse/ZF-2779 addressed (for history also
see http://framework.zend.com/issues/browse/ZF-1429 ) for 1.5, but I guess
it's out the scope because there isn't even a patch yet, right? Actually
reverting 1429 would do the tick.
This change in behavior since introduces caused quite some PITA, it works
really against the philosophy of keeping things in their realm. This
deliberate chmod tries to make Lucene do things which it shouldn't. FWIW, the
java implementation doesn't have this enforcement and thus no such problems.
I'm posting this because with the latest changes especially related to
Wildcard-Support Zend_Search_Lucene really becomes a viable alternative to the
non-PHP solutions, but the chmod() may be a can of worms waiting to be
opened ...
thanks,
- Markus
Wil Sinclair wrote:
We've been getting a lot of very useful feedback on Zend Framework
1.5.0RC1. At this time we're preparing a second release candidate to
address some of that feedback and to add a couple of features that
didn't make it in to RC1, such as LDAP authentication and the Nirvanix
web service.
The code freeze for this releases is currently scheduled for 21:00
(9:00pm) PST (GMT-8) on Friday, March 7. Framework contributors should
have completed all pending work for the 1.5.0 release by this time.
As Darby mentioned before, we have created a new release-1.5 branch. All
fixes targeted for 1.5.0RC2 must be checked in to trunk and merged to
the release-1.5 branch by code freeze. Please merge any changes that you
have previously made on trunk that should also be included in 1.5.0RC2.
During the code freeze, development in /trunk may continue as usual, but
merges to the release-1.5 branch should not be committed during this
time without the approval of a Zend liaison.
Thanks to all the ZF'ers out there who have helped us put the 1.5.0
release together- may a stable and feature-full release be our reward!
,Wil
