Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of Abhinandan.Prateek@citrix.com
 designates 103.14.252.240 as permitted sender)
From: Abhinandan Prateek <Abhinandan.Prateek@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: Re: [DISCUSS] Policy blocker?
Thread-Topic: [DISCUSS] Policy blocker?
Thread-Index: 
 AQHPLkEY2H2e8i/dikmyNVnY8bQtHJq9ob+AgAIzWYCAAAWDAIAACI2AgAAGwgCAAH2eAIAAB22AgAW9qICAAPM+gIAAdvGA
Date: Wed, 26 Feb 2014 16:20:06 +0000
Message-ID: <CF3411F3.5133F%abhinandan.prateek@citrix.com>
References: 
 <CAKprHVbPzQEe6vPuoACU0t6kmsfjjTW9=pEVwvjPVteG9PY2dA@mail.gmail.com>
 <53060741.9050600@widodh.nl>
 <CAKprHVaamqvEDDg-0y=RpdQb1e8R+eB9ORZV80VRJYk+Fy+ong@mail.gmail.com>
 <C3637609BC1C0D40A2AC70F4760C7A2D2A7CB5@SJCPEX01CL02.citrite.net>
 <CAKprHVYgvaMKaJBiO4XvxgwJkY3FfHJBLaNPdTVxJZijd1izuA@mail.gmail.com>
 <C3637609BC1C0D40A2AC70F4760C7A2D2A7D48@SJCPEX01CL02.citrite.net>
 <643B7A20-6334-4B26-8FD8-2DBB6CE201EE@gmail.com>
 <CAKprHVaF7Lnys0CYtJ8-ZkQC1bEvoR7AtngwCm5GDc4D94bgzA@mail.gmail.com>
 <C3637609BC1C0D40A2AC70F4760C7A2D2AB639@SJCPEX01CL02.citrite.net>
 <CADENRmobfaoqT3qs2vC6xP1bJ6nVGFFfXX-F9JLpg_oj46_u3w@mail.gmail.com>
In-Reply-To: 
 <CADENRmobfaoqT3qs2vC6xP1bJ6nVGFFfXX-F9JLpg_oj46_u3w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.9.131030
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D5678D493967AB44B610F028B0DB4D11@citrix.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1 this is reasonable.

On 26/02/14 8:14 pm, "Chip Childers" <chipchilders@apache.org> wrote:

>On Tue, Feb 25, 2014 at 7:13 PM, Animesh Chaturvedi
><animesh.chaturvedi@citrix.com> wrote:
>>
>> Folks since the liability of Release manager has been called out
>>explicitly for the release I want to call out that I cannot take
>>personal liability for a release and I am not sure why would anyone else
>>in Release Manager role will take up personal liability. I don't see
>>anything called out in our bylaws that states Release Manager being
>>liable.
>>
>> That being said I am seeking advice from ASF mentors and will discuss
>>it in  PMC. I  will proceed and build an RC after this issue is resolved.
>>
>> Thanks
>> Animesh
>
>A couple of things:
>
>First, we don't have any "mentors" anymore...  we're a TLP.
>
>Second, although the question of "liability" has been clarified in the
>private@ thread, I'll summarize briefly here:
>
>The reason that we follow the voting process (where the PMC votes are
>binding) and other ASF-wide policies, is so that any release is an
>"act of the foundation" and not an act of an individual.  The point is
>that if someone were to purposefully ignore policy, then they put
>themselves at risk.  The whole reason for the foundation to have it's
>policies is to protect all of the committers and contributors from
>personal liability!  So the only thing that really matters is that if
>we follow the policies of the foundation, there's nothing to worry
>about.
>
>Being a release manager is nothing to worry about...  the whole PMC is
>helping to ensure that we follow policies.  As our current 4.3 issue
>has pointed out, sometimes this means we have to slow down to fix
>something.  If something slipped through, it's still not a "liability"
>issue in practical terms.  It's just a mistake that we would then work
>to correct.
>
>Make sense?
>
>-chip