Doodle link is: http://www.doodle.com/kxpxkrvhgnd2bx5i
Appointment is as always this afternoon on IRC at 17: I probably won't be there today. Cheers, Francesco On Wed, Jan 4, 2012 at 1:23 PM, Johannes Schmitt <schmitt...@gmail.com>wrote: > Another PR that could be discussed/reviewed: > https://github.com/symfony/symfony/pull/2996 > > Cheers, > Johannes > > > On Tue, Jan 3, 2012 at 3:11 PM, Stefan Paschke > <symfony.pasc...@gmail.com>wrote: > >> Hi Franceso, hi everybody >> >> I finally could do some work on >> https://github.com/symfony/symfony/pull/786 >> >> This PR adds concurrent sessions to the Security component; I added a >> DBAL default implementation that was requested when I originally opened it. >> I would appreciate if it could be discussed in the upcoming meeting, and >> possibly still make it into 2.1 >> >> best regards >> >> Stefan >> >> On Jan 2, 2012, at 5:06 PM, Francesco Levorato wrote: >> >> Hi everybody and happy 2012! >> >> We have a IRC meeting scheduled for Thursday 5th. >> >> I will be collecting proposals for discussion topics until Wednesday >> afternoon, after that I'll publish the Doodle for voting. >> >> https://github.com/symfony/symfony/pull/2853 (suggested by Drak) >> The following were mentioned in a thread related to 2.1 release: >> >>> here is another form PR that also mentions the need for some further >>> refactoring: >>> https://github.com/symfony/symfony/pull/2015 >> >> >> >>> 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. >> >> >> Cheers, >> Francesco >> >> >> >> -- >> 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 >> > > -- > 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 > -- francesco levorato aka flevour http://flevour.net - on Twitter I am: @flevour <http://twitter.com/flevour> http://doitagainapp.com - Motivational tool for lazy people http://foopro.com - proud fooDev0 @ FooPro http://screenfony.com - symfony video tutorials -- 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
