Received: by 10.180.73.173 with SMTP id m13mr925239wiv.4.1348427406915;
        Sun, 23 Sep 2012 12:10:06 -0700 (PDT)
X-BeenThere: symfony-devs@googlegroups.com
Received: by 10.216.53.65 with SMTP id f43ls6860476wec.1.gmail; Sun, 23 Sep
 2012 12:10:02 -0700 (PDT)
Received: by 10.180.73.242 with SMTP id o18mr665052wiv.0.1348427402057;
        Sun, 23 Sep 2012 12:10:02 -0700 (PDT)
Received: by 10.180.73.242 with SMTP id o18mr665050wiv.0.1348427402046;
        Sun, 23 Sep 2012 12:10:02 -0700 (PDT)
Return-Path: <m...@pooteeweet.org>
Received: from ssl.backendmedia.com (static.84.111.9.176.clients.your-server.de. [176.9.111.84])
        by gmr-mx.google.com with ESMTPS id fb20si474981wid.3.2012.09.23.12.10.01
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 23 Sep 2012 12:10:01 -0700 (PDT)
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;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 176.9.111.84 is neither permitted nor denied by best guess record for domain of m...@pooteeweet.org) smtp.mail=...@pooteeweet.org
Received: from localhost (unknown [127.0.0.1])
	by ssl.backendmedia.com (Postfix) with ESMTP id EE3DA5EFE377
	for <symfony-devs@googlegroups.com>; Sun, 23 Sep 2012 19:10:03 +0000 (UTC)
X-Virus-Scanned: amavisd-new at backendmedia.com
Received: from ssl.backendmedia.com ([127.0.0.1])
	by localhost (hq2.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zwpnkREbL210 for <symfony-devs@googlegroups.com>;
	Sun, 23 Sep 2012 21:10:03 +0200 (CEST)
Received: from [192.168.0.177] (77-58-147-243.dclient.hispeed.ch [77.58.147.243])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: m...@pooteeweet.org)
	by ssl.backendmedia.com (Postfix) with ESMTPSA id 9AE385EFE376
	for <symfony-devs@googlegroups.com>; Sun, 23 Sep 2012 21:10:03 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: [symfony-devs] A formal release process proposal
From: Lukas Kahwe Smith <m...@pooteeweet.org>
In-Reply-To: <505DBC00.5060...@symfony.com>
Date: Sun, 23 Sep 2012 21:10:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <806213A3-D7E7-4695-A691-9500719D9...@pooteeweet.org>
References: <5056AE99.9050...@symfony.com> <b92fd742-6604-4170-897b-faf376d33a7e@googlegroups.com> <E4242581-AAA1-4833-837E-586A743A2...@pooteeweet.org> <505C0CFF.5020...@symfony.com> <1147DA68-59EA-4EFB-B10E-631E53498...@pooteeweet.org> <505DBC00.5060...@symfony.com>
To: symfony-devs@googlegroups.com
X-Mailer: Apple Mail (2.1498)


On Sep 22, 2012, at 15:24 , Fabien Potencier =
<fabien.potenc...@symfony-project.com> wrote:

> On 9/22/12 9:19 AM, Lukas Kahwe Smith wrote:
>> On 21.09.2012, at 08:45, Fabien Potencier =
<fabien.potenc...@symfony-project.com> wrote:
>>=20
>>> * merging 2.0 into 2.1 is a major PITA (just for me actually) as all =
the tests were moved in 2.1, and because the form framework evolved a =
lot as well, so it takes me more and more time to merge 2.0 into 2.1;
>>>=20
>>> * we can decide to keep the 2 months period but still accept =
security fixes for a longer period of time (6 months).
>>=20
>> we talked about changing the merging policy in Denver. ie. we would =
merge bug fixes to master and then merge it down ro previous releases. i =
dont remember the pros and cons we listes back then. but it might become =
more necessary to enable delegation of responsibility.
>=20
> I think the current worflow is the best one as we can check very =
easily which patches/PRs are merged in which branches. So, I don't think =
that changing this strategy would be good.


yes .. but if the current approach means everything for all branches =
needs to go through you, then we have a scalability issue. even if some =
things might be slowed down but then having the option to delegate work =
to multiple people, we might still have a higher "through put".

regards,
Lukas Kahwe Smith
m...@pooteeweet.org