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 (athena.apache.org: domain of akarasulu@gmail.com
 designates 74.125.46.31 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=B2hpg4wgG9H3hRjb5s5vRfQc6x/72MCxT3H5/f1/cKZVT/upUP6NTRpoWNiB83GZep
         Jx0JctJ1mi9gmM6JwBLqXLJPDyKh4GSi/cnkRKiOPru+vF7K5ulX397nc3pUf3dD6cZA
         zJqtXWOrk4+7nRYw8MEmsURk2XV3YQz2YsFfw=
Message-ID: <a32f6b020807131713w73a2de90xc3f64908bd67162f@mail.gmail.com>
Date: Sun, 13 Jul 2008 20:13:16 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [Project] Project pom release 11 is same as 10
In-Reply-To: <487A9499.8070500@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_69156_29363166.1215994396958"
References: <a32f6b020807131201x429fcf49v1acd4ae0b25e838@mail.gmail.com>
	 <487A9499.8070500@apache.org>

------=_Part_69156_29363166.1215994396958
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Felix,

On Sun, Jul 13, 2008 at 7:49 PM, Felix Knecht <felixk@apache.org> wrote:

> Alex Karasulu schrieb:
>
>> Hi all,
>>
>> Just a note to the community.  As I was releasing ApacheDS 1.5.3 I noticed
>> that we were still set to version 10 of the TLP pom.  The latest version
>> that I just released is 11.  Both are poms are identical besides the
>> versions and URLs into svn where the tags can be found.
>>
>
> It's quite a time ago I had the last time a 'silly' question, but
>
> Why do we need to release then a new version of the pom? Maybe I missed
> something but IMO if nothing has changed we should still be able to use pom
> version 10, don't we?
>
>
You're right we did not need to release 11 at all.  I accidentally released
it because when I looked at the project/trunk/pom.xml it was at
11-SNAPSHOT.  I presumed shared, apacheds, daemon and installers trunks used
this 11-SNAPSHOT.  I also presumed that it was bumped up to 11-SNAPSHOT
because changes were induced to 10.

Next time I will check to make sure there are no differences before
releasing.  This pom should not be bumped on each release iteration to the
next SNAPSHOT.  Part of the problem is Maven's release plugin which does
this automatically.

Regards,
Alex

-- 
Microsoft gives you Windows, Linux gives you the whole house ...

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

Hi Felix,<br><br><div class="gmail_quote">On Sun, Jul 13, 2008 at 7:49 PM, Felix Knecht &lt;<a href="mailto:felixk@apache.org">felixk@apache.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alex Karasulu schrieb:<div class="Ih2E3d"><br>
<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>
Just a note to the community. &nbsp;As I was releasing ApacheDS 1.5.3 I noticed that we were still set to version 10 of the TLP pom. &nbsp;The latest version that I just released is 11. &nbsp;Both are poms are identical besides the versions and URLs into svn where the tags can be found. <br>

</blockquote>
<br></div>
It&#39;s quite a time ago I had the last time a &#39;silly&#39; question, but<br>
<br>
Why do we need to release then a new version of the pom? Maybe I missed something but IMO if nothing has changed we should still be able to use pom version 10, don&#39;t we?<br><font color="#888888">
<br>
</font></blockquote></div><br>You&#39;re right we did not need to release 11 at all.&nbsp; I accidentally released it because when I looked at the project/trunk/pom.xml it was at 11-SNAPSHOT.&nbsp; I presumed shared, apacheds, daemon and installers trunks used this 11-SNAPSHOT.&nbsp; I also presumed that it was bumped up to 11-SNAPSHOT because changes were induced to 10.<br clear="all">
<br>Next time I will check to make sure there are no differences before releasing.&nbsp; This pom should not be bumped on each release iteration to the next SNAPSHOT.&nbsp; Part of the problem is Maven&#39;s release plugin which does this automatically. <br>
<br>Regards,<br>Alex<br><br>-- <br>Microsoft gives you Windows, Linux gives you the whole house ...

------=_Part_69156_29363166.1215994396958--