Those two items you mentioned can be done by the community at large.
The point of a release manager would be introducing a couple more benevolent dictators; rather than someone who has a "rank for show" but no true extra responsibilities. It would need to be something that actually means they can do things that normal community members or even core team members (which is essentially currently a rank to show they contribute a lot of quality code rather than more responsibilities) can't necessarily do such as making releases, making final decisions on features inclusion etc. All of this is in consultation with the community but everything needs a leader. Currently we have Fabien but Symfony is growing and too big a project for one man to bear the brunt of all of these things (think of the bus scenario). Thanks Michael Cullum From: symfony-devs@googlegroups.com [mailto:symfony-devs@googlegroups.com] On Behalf Of Pascal Sent: 10 October 2012 17:19 To: symfony-devs@googlegroups.com Subject: Re: [symfony-devs] release management Hi, Does "it has to be" someone else than Fabien ? I would rather see him focusing on this role (Release Manager of master) instead of everything else he does actually. Nominating people for "Issue triage", "PR triage/checker", "..." instead would be great in my opinion. What do you guys think ? Pascal On Wed, Oct 10, 2012 at 4:08 PM, Lukas Kahwe Smith <m...@pooteeweet.org> wrote: On Sep 10, 2012, at 18:05 , "Michael C" <m...@michaelcullum.com> wrote: > Whilst it should change between releases I can't see why someone can't do it > twice (or more); just perhaps have a two-three versions break. So the 2.2 RM > could next become an RM for 2.4 or 2.5 sure. the point of it changing is to prevent this from becoming in-transparent. furthermore i think its a great way for new developers on the team to be recognized for the trust they have build within the community. 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 <mailto:symfony-devs%2bunsubscr...@googlegroups.com> For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -- Pascal -- 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
