Le 27/04/2012 12:16, Thomas Lundquist a écrit :
On Fri, Apr 27, 2012 at 02:39:26AM -0700, keymaster wrote:
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.
Very good point here.
Another one is; Will there be BC breaks at all with 2.0 -> 2.1 without
Validation/Forms?
The answer seems to be "Yes" and as long as that remains true I have a
slight feeling that pissing off the users with BC breaks for each minor
release (2.0 -> 2.1 and then bigger breaks 2.1 to 2.2) is not a very
good idea.
symfony 1 was bad in these matters, lets not go back there please.
One problem I had with symfony 1 was that plugins broke and never
got repaired by their maintainers when 1.2 got into 1.3/1.4 and that
made upgrades hell.
And that might just as well happen here. If we do this *once* for the
whole life of 2.X it may be OK and you will know that using 2.1
will keep you and the third party bundles happy and alive.
But picking a third party bundle now, when you *know* that it will
not work when 2.2 is out is not easy. It may be another year and you
never know what happens with the maintenance in that time.
And yes; "Just fix it yourself then" is an answer and possible but it
will still piss the users/developers off and make more people than
me reconsider the choice of using Symfony again.
I am going to invest quite a lot of time on different bundles and applications
the next year and without the knowledge that I can do that without too much
BC hassle I will start discussing alternatives with my collegues.
And I am pretty sure I'm not the only one. If I am, it's not much
of a loss but then again..
Thomas.
The goal is to break BC in forms only once (between 2.1 and 2.2, by
reverting the Form BC breaks in 2.1). If we keep the current code for
2.1, it will be breaking BC twice as the current Form code is not
totally mature and needs some more changes (look at bernhard's pending
pull requests). If you want to do all breaks for 2.1, it means delaying
the release, which is exactly was we are trying to avoid.
Btw, the 2.0 release was advocating that the Form component was not
considered as stable and that changes will occur later.
--
Christophe | Stof
--
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
