+1 Daniel On Sat, Mar 3, 2012 at 4:09 PM, Daniel A.Tiecher <datiec...@gmail.com>wrote:
> What about organizing a Bug Jam for the 2.1 milestone to get the community > together and help lower the issues count on Github? > > Maybe going even further and grouping the issues into difficulty (in terms > of needed core knowledge) and time effort to complete? > > I can't help but think that something along these lines would help closing > some of those issues and bring us closer to a 2.1 release. =) > > Em sábado, 3 de março de 2012 13h10min40s UTC-3, Lukas Smith escreveu: > >> >> On Feb 29, 2012, at 06:39 , Fabien Potencier wrote: >> >> > IRC should be used for things that cannot happen on the mailing-list or >> on Github: like planning 2.1 or discussing something that we cannot agree >> on with just a technical discussion on Github. >> >> >> indeed 2.1 is something we need to talk about again. >> >> - composer has made a major step forward, but there are still reliability >> issues with github it seems and many popular Bundles are missing >> composer.json's >> - the pipeline of open PR's seems to be staying between 40-60 but nothing >> all too major (am i overlooking something or someone working on something >> in secret?) >> - form/validation has gotten a lot of love but there are still plenty of >> open tickets in all areas https://github.com/symfony/** >> symfony/issues?sort=created&**direction=desc&state=open&** >> page=1&milestone=6<https://github.com/symfony/symfony/issues?sort=created&direction=desc&state=open&page=1&milestone=6> >> >> so i think we should start clarifying our time line. again i think we >> should not delay release's too far out of a 6 month cycle and instead we >> should drop features instead. >> >> regards, >> Lukas Kahwe Smith >> m...@pooteeweet.org >> >> > Em sábado, 3 de março de 2012 13h10min40s UTC-3, Lukas Smith escreveu: > >> >> On Feb 29, 2012, at 06:39 , Fabien Potencier wrote: >> >> > IRC should be used for things that cannot happen on the mailing-list or >> on Github: like planning 2.1 or discussing something that we cannot agree >> on with just a technical discussion on Github. >> >> >> indeed 2.1 is something we need to talk about again. >> >> - composer has made a major step forward, but there are still reliability >> issues with github it seems and many popular Bundles are missing >> composer.json's >> - the pipeline of open PR's seems to be staying between 40-60 but nothing >> all too major (am i overlooking something or someone working on something >> in secret?) >> - form/validation has gotten a lot of love but there are still plenty of >> open tickets in all areas https://github.com/symfony/** >> symfony/issues?sort=created&**direction=desc&state=open&** >> page=1&milestone=6<https://github.com/symfony/symfony/issues?sort=created&direction=desc&state=open&page=1&milestone=6> >> >> so i think we should start clarifying our time line. again i think we >> should not delay release's too far out of a 6 month cycle and instead we >> should drop features instead. >> >> 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+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
