Code freeze for 1.5.0RC2

[wllm]

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

[Markus Fischer-5]

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
>

[oetting]

Hi,
Is Zend_Build going to make it into 1.5? There has not been much activity on the list about Zend_Build/_Console lately.

/Jacob Oettinger

[wllm]

We are hoping to ship it in a separate 'incubator' folder for 1.5,
although at the moment we're not sure it will make it in. I haven't had
a chance to work on it for almost 2 months, so Ralph has had to come up
to speed with a relatively large project and work on it himself. There
are certainly opportunities for community members to help out here. ;)
As for why we would ship it in incubator vs. a full-fledged core
component:

a) It simply is not mature enough to meet our quality guidelines.
b) This is a very different component from other ZF components. For
example, none of this code is likely to be run to answer a request- it
is really a different environment. We're also creating a whole new
interface and *huge* extension point for the user. We don't feel like
the community has had enough time to look at this, so we're not ready to
commit to API's and UI's just yet. After getting relatively little
feedback on my proposals earlier in the process, we decided it would be
best to get a prototype in the hands of users ASAP so they can play with
it and really get to know it. That would be the purpose of shipping
Zend_Build and CLI in incubator with 1.5.

We should have a definite answer on this in the next few days. I will
mail the list when we have made a go/no go decision. In any case, it
won't hold up 1.5, and it will be available soon for evaluation even if
it doesn't make it in to the 1.5 package.

Thanks.
,Wil

> -----Original Message-----
> From: oetting [mailto:jacob@...]
> Sent: Monday, March 03, 2008 11:39 PM
> To: fw-general@...
> Subject: Re: [fw-general] Code freeze for 1.5.0RC2
>
>
> Hi,
> Is Zend_Build going to make it into 1.5? There has not been much
> activity on
> the list about Zend_Build/_Console lately.
>
> /Jacob Oettinger
> --
> View this message in context: http://www.nabble.com/Code-freeze-for-
> 1.5.0RC2-tp15814739s16154p15821789.html
> Sent from the Zend Framework mailing list archive at Nabble.com.

[oetting]

Ok, thank you for the update. The arguments for holding of on the core-
inclusion sound reasonable.

> I haven't had
> a chance to work on it for almost 2 months, so Ralph has had to come  
> up
> to speed with a relatively large project and work on it himself. There
> are certainly opportunities for community members to help out here. ;)

If Ralph has tasks that can be delegated, I would like to help.

Jacob

On 04/03/2008, at 20.06, Wil Sinclair wrote:

> We are hoping to ship it in a separate 'incubator' folder for 1.5,
> although at the moment we're not sure it will make it in. I haven't  
> had
> a chance to work on it for almost 2 months, so Ralph has had to come  
> up
> to speed with a relatively large project and work on it himself. There
> are certainly opportunities for community members to help out here. ;)
> As for why we would ship it in incubator vs. a full-fledged core
> component:
>
> a) It simply is not mature enough to meet our quality guidelines.
> b) This is a very different component from other ZF components. For
> example, none of this code is likely to be run to answer a request- it
> is really a different environment. We're also creating a whole new
> interface and *huge* extension point for the user. We don't feel like
> the community has had enough time to look at this, so we're not  
> ready to
> commit to API's and UI's just yet. After getting relatively little
> feedback on my proposals earlier in the process, we decided it would  
> be
> best to get a prototype in the hands of users ASAP so they can play  
> with
> it and really get to know it. That would be the purpose of shipping
> Zend_Build and CLI in incubator with 1.5.
>
> We should have a definite answer on this in the next few days. I will
> mail the list when we have made a go/no go decision. In any case, it
> won't hold up 1.5, and it will be available soon for evaluation even  
> if
> it doesn't make it in to the 1.5 package.
>
> Thanks.
> ,Wil
>
>> -----Original Message-----
>> From: oetting [mailto:jacob@...]
>> Sent: Monday, March 03, 2008 11:39 PM
>> To: fw-general@...
>> Subject: Re: [fw-general] Code freeze for 1.5.0RC2
>>
>>
>> Hi,
>> Is Zend_Build going to make it into 1.5? There has not been much
>> activity on
>> the list about Zend_Build/_Console lately.
>>
>> /Jacob Oettinger
>> --
>> View this message in context: http://www.nabble.com/Code-freeze-for-
>> 1.5.0RC2-tp15814739s16154p15821789.html
>> Sent from the Zend Framework mailing list archive at Nabble.com.
>