Phil Steitz wrote:
+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
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
+1 from me
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
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
This is not a Jakarta thing anymore :)
Mvgr,
Martin
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
+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
Rahul Akolkar wrote:
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
I haven't yet understood why we need to release anything from the
sandbox at all. Sure, reproducibility is a good thing, but I doubt the
builds are radically
On 6/24/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Rahul Akolkar wrote:
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
I haven't yet understood why we need to release anything from the
sandbox at all. Sure, reproducibility is
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
This will be the first release and is important because it enables
reproducible
On 6/24/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Rahul Akolkar wrote:
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
I haven't yet understood why we need to release anything from the
sandbox at all. Sure, reproducibility is
Rahul Akolkar wrote:
On 6/24/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Rahul Akolkar wrote:
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
I haven't yet understood why we need to release anything from the
sandbox at all.
On 6/24/07, Torsten Curdt [EMAIL PROTECTED] wrote:
On 23.06.2007, at 18:59, Rahul Akolkar wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] 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
On 23.06.2007, at 18:59, Rahul Akolkar wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] 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
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
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] 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
On 6/23/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
This will be the first release and is important because it enables
reproducible builds and site generation for the sandbox components.
Since you have a policy against releasing sandbox
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
This will be the first release and is important because it enables
reproducible builds and site generation for the sandbox components.
Since you have a policy against releasing sandbox components, why not
just deploy snapshots of the
Phil Steitz wrote:
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] 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
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] 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
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
I haven't yet understood why we need to release anything from the
sandbox at all. Sure, reproducibility is a good thing, but I doubt the
builds are radically irreproducible without this
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
This will be the first release and is important because it enables
reproducible builds and site generation for the sandbox components.
21 matches
Mail list logo