We still have a security regression in master from a commit in mid November (https://github.com/symfony/symfony/issues/2679) which should be addressed.
Then there is also the question of changing listener priorities ( https://github.com/symfony/symfony/issues/2680) which has also the potential to create silent security holes in applications migrating from 2.0 to 2.1. Both of these should best resolved before 2.1 one way or another. Cheers, Johannes On Thu, Dec 22, 2011 at 7:58 PM, Fabien Potencier < fabien.potenc...@symfony-project.com> wrote: > On 12/22/11 7:48 PM, Lukas Kahwe Smith wrote: > >> >> On Dec 21, 2011, at 14:38 , Fabien Potencier wrote: >> >> I've just sent a PR for streamed responses: https://github.com/symfony/* >>> *symfony/pull/2935 <https://github.com/symfony/symfony/pull/2935> >>> >>> Any feedback welcomed. >>> >> >> >> guess you got that feedback you were asking for :) >> > > Yes! > > > at any rate wanted to ask what your tentative time frame for 2.1 looks >> like. >> i guess we are still well within the once discussed 6 month cycle but of >> course the quick 2.1 after 2.0 we once had hoped for did not pan out. >> >> generally i dont expect that we need any sort of alpha/beta cycle for 2.1 >> as things are quite stable overall from my POV. >> >> so i am thinking a couple of RC's is all we need. >> Doctrine seems to be fairly good on schedule to do its releases, so the >> main outside variable remains composer. >> As for our tasks, I would say at the earliest we could look to start RC's >> mid January giving us a release end of January or early February. >> That being said, we really should not slip out of February, especially as >> we are not longer aiming to make 2.1 the LTS, we should rather strip >> features than wait with a stable release. >> >> So to conclude imho anything that isnt ready for an RC in late January >> should be dropped from the release. >> > > I agree with you on most the things you have mentioned. I would like to > release 2.1 RC1 mid-January if possible and the stable release after a few > RCs. So, 2.1 stable should be out in March. > > Fabien > > > regards, >> Lukas Kahwe Smith >> m...@pooteeweet.org >> >> >> >> > -- > 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 symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscribe@**googlegroups.com<symfony-devs%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/**group/symfony-devs?hl=en<http://groups.google.com/group/symfony-devs?hl=en> > -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
