Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates
 209.85.132.245 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=JPninFBQc63wk0ZVbuE0kB64V7wc9DnoX3RJ8SyeuKToFEPl+p2Lcz8V3CZIBr75Lnrm0j+FgHjk/mkFj6TdrXWk8VH0JE1zx67NbQMsjGy2znyvaSL/duoO33nidTw29TeMlQ8ozW91a3E2uNzx8jnr8q1Xvpzmj07tX++SFfM=
Message-ID: <a32f6b020705280811x602fe9bfycf21821e9acf2b07@mail.gmail.com>
Date: Mon, 28 May 2007 11:11:51 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [VOTE] Policy for Managing TLP POM
In-Reply-To: <a32f6b020705221800j5cc9e0a0v645d9fd220fbf812@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_28053_19800971.1180365111797"
References: <a32f6b020705221800j5cc9e0a0v645d9fd220fbf812@mail.gmail.com>

------=_Part_28053_19800971.1180365111797
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

+1
Alex

On 5/22/07, Alex Karasulu <akarasulu@apache.org> wrote:
>
> Hi all,
>
> I compiled some documentation talking about how we should handle a parent
> POM for our TLP
> so all subprojects can inherit from it.  We have been using it incorrectly
> and have been loosing
> track of it. I explain all this and expose some simple policy (6 rules)
> that will help us keep this
> all straight [1].
>
> Please read this and let's vote on it make it official.
>
> [  ] +1 Apply this policy/process for TLP POM management
> [  ] +/-0 Abstain - don't understand or don't care
> [  ] -1 Do *NOT* apply this policy for TLP POM management
>
> -- Alex
>
> -------
> [1] - http://cwiki.apache.org/DIRxDEV/top-level-pom-management-policy.html
>
>
>
>

------=_Part_28053_19800971.1180365111797
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

+1<br>Alex<br><br><div><span class="gmail_quote">On 5/22/07, <b class="gmail_sendername">Alex Karasulu</b> &lt;<a href="mailto:akarasulu@apache.org">akarasulu@apache.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>I compiled some documentation talking about how we should handle a parent POM for our TLP<br>so all subprojects can inherit from it.&nbsp; We have been using it incorrectly and have been loosing<br>track of it. I explain all this and expose some simple policy (6 rules) that will help us keep this
<br>all straight [1].&nbsp;  <br><br>Please read this and let&#39;s vote on it make it official.<br><br>[&nbsp; ] +1 Apply this policy/process for TLP POM management<br>[&nbsp; ] +/-0 Abstain - don&#39;t understand or don&#39;t care<br>

[&nbsp; ] -1 Do *NOT* apply this policy for TLP POM management <br><br>-- Alex<br><br>-------<br>[1] - <a href="http://cwiki.apache.org/DIRxDEV/top-level-pom-management-policy.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://cwiki.apache.org/DIRxDEV/top-level-pom-management-policy.html
</a><br><br><br>
</blockquote></div><br>

------=_Part_28053_19800971.1180365111797--