Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Continuous release review
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: <CFAB643C.22DBD%aharui@adobe.com>
Date: Wed, 28 May 2014 13:24:39 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <C174F6FF-BC2C-43F0-8191-CDA3D25D4E61@jaguNET.com>
References: 
 <CAOFYJNaqACY-JXUesx-V0PnsiCCkfVo_xKdEMO-N5Nt7Y_JTFQ@mail.gmail.com>
 <6F8EDB3F-12C5-4D0C-A379-E9AB4F99F391@jaguNET.com>
 <B97B3DBD-2937-4BE0-A127-92ED5B27ED84@jaguNET.com>
 <CFAB643C.22DBD%aharui@adobe.com>
To: legal-discuss@apache.org


On May 28, 2014, at 1:16 PM, Alex Harui <aharui@adobe.com> wrote:
> 
> What I think several of us want to explore is whether the current release
> policy/process can be automated in places and still be serious about it.
> 

Sure, and of course I'm sure there are places where
some stuff can be automated. But it seems to me that
most people are chaffing against the "3 +1 votes" and
the "72 hour" rules... We need to recall that creating
a release != actually releasing the release, as well :)


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org