On Apr 27, 2012, at 12:06 , Michał Piotrowski wrote:

> Hi,
> 
> 2012/4/27 keymaster <[email protected]>:
>> 
>> If we go with 2.1 = (Master less Form/Validator BC breaks), won't that cause
>> some confusion and destabilization in 3rd party land?
>> 
>> Many 3rd party bundles have developed against Master and work fine. They
>> were slated to be the "2.1 compatable" versions of their bundles.
>> 
>> If we create a 2.1 branch, but revert some updates out of it, than many
>> these 3rd party bundles which were tracking Master, will not work in 2.1.
>> They may also have to revert some code to be compatable with the "new" 2.1
>> (as opposed to the old Master).
>> 
>> The new 2.1 will necessarily be less stable than the Master, by definition,
>> since it's code base has soaked less than the Master.
>> 
>> I understand the desire to maintain stability by not introducing BC breaks,
>> but if they are already in Master and being used, then it may be even more
>> destabilizing (and confusing for the entire community) to create a new 2.1
>> branch with a subset of software with the Form/Validator stuff removed.
>> 
> 
> Recently I started to develop a new Symfony 2.1 application. Described
> changes do not cause any problems for me, but I fully agree with what
> keymaster wrote. There are bundles that works fine with actual Symfony
> master branch - form/validation changes may break these bundles. New
> Symfony release without hundreds of working bundles it is not
> something that users would like. From my POV it is better to release
> Symfony 2.1 with some form/validation BC breaks, than revertiong all
> these changes and to create something like a Frankenstein which is not
> so well tested :)


reverting the changes in the Bundles will be trivial and any Bundle author that 
updated to master (aka 2.1) already will hear about this change back too .. so 
I am sure they will get updated just as quickly. more importantly it just means 
that their 2.1 version now becomes the 2.2 version.

regards,
Lukas Kahwe Smith
[email protected]



-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to