1.5 and backwards compatibilty. . .

Hi all, just a quick reminder that our intention is to make
1.5 a
completely backwards compatible release.

*If you have made an API or behavior change for 1.5 that is
not
backwards compatible, please notify me ASAP.*

To reiterate the team's position on backwards compatibility:
not all
Zend Framework releases will be backwards compatible, but
the intention
is to reserve BC breaks for major releases and only with
good
justification. Of course, backwards compatibility is only
guaranteed for
general availability releases; we will not make any
guarantees explicit
or otherwise for BC with 0.x, preview releases, or release
candidates.
It might seem counter-intuitive, but this relatively strict
backwards
compatibility policy allows us to continue looking forwards
as much as
possible. Every non-BC release will leave a set of users who
are either
unable or unwilling to upgrade their application to use the
latest
version of the framework. This leads to more effort
supporting older
versions of the framework, which ultimately comes off the
bottom line of
effort we can put in to future releases. We want you to get
the most out
of your existing investment in ZF, so we believe that this
is the best
way we can deliver value for now and for the future.

Thanks!
,Wil

wllm wrote:
> 
> *If you have made an API or behavior change for 1.5
that is not
> backwards compatible, please notify me ASAP.*
> 

In order to fix http:
//framework.zend.com/issues/browse/ZF-1308 I changed
the method name, however it was previously declared as
private thus I
suppose there's no BC issue here.

-- 
View this message in context: http://www.nabble.com/1.
5-and-backwards-compatibilty.-.-.-tp14915193s16154p14921159.
html
Sent from the Zend Framework mailing list archive at
Nabble.com.

That should be A-OK. Only changes that could potentially
break existing
applications would be a BC issue.

,Wil

> -----Original Message-----
> From: Simone Carletti [mailto:wepposgmail.com]
> Sent: Thursday, January 17, 2008 7:05 AM
> To: fw-generallists.zend.com
> Subject: Re: [fw-general] 1.5 and backwards
compatibilty. . .
> 
> 
> 
> wllm wrote:
> >
> > *If you have made an API or behavior change for
1.5 that is not
> > backwards compatible, please notify me ASAP.*
> >
> 
> In order to fix http:
//framework.zend.com/issues/browse/ZF-1308 I
> changed
> the method name, however it was previously declared as
private thus I
> suppose there's no BC issue here.
> 
> --
> View this message in context: http://www.n
abble.com/1.5-and-backwards-
> compatibilty.-.-.-tp14915193s16154p14921159.html
> Sent from the Zend Framework mailing list archive at
Nabble.com.

We still have the newline problem in Zend_Mime. The current
task is  
ZF-1886. It was changed from rn to n, which is not
standard, but  
fixed some problems. Now others have problems and want it to
change  
from n to rn, which is more correct, but would again
raise the  
issue we fixed the last time. It's a lose:lose situation and
it breaks  
in some kind backwards compatibility.

nico

Wil Sinclair wrote:
> That should be A-OK. Only changes that could
potentially break  
> existing
> applications would be a BC issue.
>
> ,Wil
>
>> -----Original Message-----
>> From: Simone Carletti [mailto:wepposgmail.com]
>> Sent: Thursday, January 17, 2008 7:05 AM
>> To: fw-generallists.zend.com
>> Subject: Re: [fw-general] 1.5 and backwards
compatibilty. . .
>>
>>
>>
>> wllm wrote:
>>>
>>> *If you have made an API or behavior change for
1.5 that is not
>>> backwards compatible, please notify me ASAP.*
>>>
>>
>> In order to fix http:
//framework.zend.com/issues/browse/ZF-1308 I
>> changed
>> the method name, however it was previously declared
as private thus I
>> suppose there's no BC issue here.
>>
>> --
>> View this message in context: http://www.nabble.com/
1.5-and- 
>> backwards-
>> compatibilty.-.-.-tp14915193s16154p14921159.html
>> Sent from the Zend Framework mailing list archive
at Nabble.com.
>