I have read somewhere that LTS version will be 2.2 which will be released 
on July/August of this year, as stated by @fabpot here: 
https://github.com/symfony/symfony/pull/3378#issuecomment-5377420 
There are many new features which are on master for quite a long time but 
not on 2.0, so I guess the idea is to have a release with those features 
available. 

El viernes, 27 de abril de 2012 07:35:32 UTC-4, Thomas Lundquist escribió:
>
> On Fri, Apr 27, 2012 at 12:22:47PM +0200, Christophe COEVOET wrote: 
>
> > 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). 
>
> But the result is that BC breaks *twice* since I've understood that there 
> will be minor breaks between 2.0 and 2.1 even without these big changes. 
>
> > 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. 
>
> It is *a lot* better to wait until ready and so all BC breaks in 
> one go rather than breaking BC between every minor release. 
>
> Then you can explain, document and prepare users and developers 
> for this. They will understand. 
>
> And which one is planned to be an LTS? 2.1 with broken forms or 2.2 
> which will be out "some time"? 
>
> > Btw, the 2.0 release was advocating that the Form component was not 
> > considered as stable and that changes will occur later. 
>
> Yes, but not like years after 2.0, thats way too long time. 
>
> People are investing alot of time and money on applications on this 
> and they want to be able to maintain and use this for many years. 
>
> This is why we want an LTS. But when that never shows up? 
>
> Please keep *all* BC breaks in 2.1, freeze it as soon as possible and 
> fix the bugs. Then release this as the LTS or promise no more BC breaks 
> in 2.X so that people can trust they won't be in a maintenance quagmire. 
>
> If 2.X ends up being just as messy as 1.0 I'm afraid people will steer 
> away, 
> either with a fork or onto something else. 
>
> I do not want either. 
>
>
> Thomas. 
>

-- 
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