+1 - need to do this anyway.
On 6/29/07, Dennis Lundberg <[EMAIL PROTECTED]> 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.
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
