Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <468B9A97.5000109@mdh.se>
Date: Wed, 04 Jul 2007 15:03:19 +0200
From: Dennis Lundberg <dennis.lundberg@mdh.se>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [RESULT] [VOTE] Release commons-sandbox-parent 1
References: <467D2064.2080609@apache.org>
 <46856220.2080209@apache.org>	 <46857402.7020708@apache.org>
 <8a81b4af0706291535p45a0b6bk161d9b308ea5b174@mail.gmail.com>
In-Reply-To: <8a81b4af0706291535p45a0b6bk161d9b308ea5b174@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Phil Steitz wrote:
> +1 - need to do this anyway.
> 
> On 6/29/07, Dennis Lundberg <dennisl@apache.org> wrote:
>> Hmm, it seems that I spoke too soon. We need a place in subversion to
>> put the tagged release. Since the pom is currently in sandbox-trunks
>> there simply is no tags directory to put the release in.
>>
>> I propose that we move the sandbox parent out of sandbox-trunks and into
>> a commons-sandbox-parent directory in commons proper. That would make it
>> a sibling to commons-parent.

Done.

I also deployed the pom. There is one glitch with the release process 
for it though. When you do "mvn release:perform" the default goals for 
the deploy plugin is "deploy, deploy:site". This means that it deployed 
the site for the sandbox-parent, which doesn't really exist. Anyway, I 
managed to copy the correct page from the production server before the 
site was synced from people. Just something to remember if we ever do 
another release of the sandbox parent.

>> The only thing left in sandbox-trunks then would be the site for the
>> sandbox, which consists of one (1) page. That could easily be moved down
>> into a sandbox-site directory, that would be a sibling to the sandbox
>> components.
>>
>> Thoughts?
>>
>> Dennis Lundberg wrote:
>> > The results are in:
>> >
>> > +1
>> > Dennis Lundberg
>> > Torsten Curdt
>> > Niall Pemberton
>> >
>> > -0
>> > Rahul Akolkar
>> >
>> >
>> > I will proceed with the release.
>> >
>> >
>> > Dennis Lundberg wrote:
>> >> Hi,
>> >>
>> >> It is time to release version 1 of the commons-sandbox-parent. The
>> >> latest changes includes updating the parent to commons-parent-3 and
>> >> locking down the versions for plugins. Note that I have changed the
>> >> artifactId to commons-sandbox-parent, to have a consistent naming
>> >> scheme (compare it to commons-parent).
>> >>
>> >> This will be the first release and is important because it enables
>> >> reproducible builds and site generation for the sandbox components.
>> >>
>> >> This vote is for revision 550041, which will have its version number
>> >> changed to 1 when the release is done. A SNAPSHOT has been deployed to
>> >> the Apache snapshot repo if you want to take it for a spin.
>> >>
>> >> [ ] +1
>> >> [ ] =0
>> >> [ ] -1
>> >>
>> >
>> >
>>
>>
>> -- 
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org