                                                                                                                                                                                                                                                                
Received-SPF: neutral (google.com: 176.9.111.84 is neither permitted nor denied by best guess record for domain of m...@pooteeweet.org) client-ip=176.9.111.84;
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [symfony-devs] release management
From: Lukas Kahwe Smith <m...@pooteeweet.org>
In-Reply-To: <01b901cd8f6e$262d7420$72885c...@michaelcullum.com>
Date: Wed, 10 Oct 2012 18:08:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC417F68-6EA0-4E14-AEF7-F94333C10...@pooteeweet.org>
References: <C95BF42D-5FD5-483C-B7E7-01C4F6CEB...@pooteeweet.org> <01b801cd8f6c$f4159ef0$dc40dc...@michaelcullum.com> <43D9D304-D1F6-43B9-86AB-5E408CD0D...@pooteeweet.org> <01b901cd8f6e$262d7420$72885c...@michaelcullum.com>
To: symfony-devs@googlegroups.com


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