On 1/2/07, Dan Fabulich <[EMAIL PROTECTED]> wrote:
Wendy Smoak wrote:
> On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> > > From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> > >
> > > If I understand correctly, the problem is that a 'staged' release
> > > still contains a SNAPSHOT keyw
Wendy Smoak wrote:
> On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> > > From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> > >
> > > If I understand correctly, the problem is that a 'staged' release
> > > still contains a SNAPSHOT keyword in the metadata/filename?
> >
> > Yes, that's th
On 22 Dec 06, at 10:03 PM 22 Dec 06, Craig McClanahan wrote:
On 12/22/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> > From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> >
> > If I understand correctly, the problem is that a 'staged' release
On 22 Dec 06, at 9:45 PM 22 Dec 06, Wendy Smoak wrote:
On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
>
> If I understand correctly, the problem is that a 'staged' release
> still contains a SNAPSHOT keyword in the metadata/filename?
Y
On 12/23/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 12/22/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> > > From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> > >
> > > If I understand correctly, the problem is that a 'staged' rele
On 12/22/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> > From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> >
> > If I understand correctly, the problem is that a 'staged' release
> > still contains a SNAPSHOT keyword in the metadata/filename?
On 12/22/06, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
>
> If I understand correctly, the problem is that a 'staged' release
> still contains a SNAPSHOT keyword in the metadata/filename?
Yes, that's the problem.
I would agree, but that's not ho
Comments inline...
Brett Porter wrote:
> Does this cover the whole topic?
>
http://docs.codehaus.org/display/MAVENUSER/BEA+Maven+Requirement+Documen
ts
I'd say that highlights a lot of the most important requirements; it's
probably best read together with the blog article as well.
http://darkfor
Comments inline...
> -Original Message-
> From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 14, 2006 5:07 AM
> To: Maven Developers List
> Subject: Re: Who should use SNAPSHOT when? RE: The Future of the
Release
> Process.
>
> Hi,
>
OK, I've finally written up the Compass way of doing things. I've got
it as a blog article for easier reading (and HTML formatting), but I'm
also including the text below.
http://darkforge.blogspot.com/2006/12/compass-as-compared-with-mavens.ht
ml
In this article, I'll describe some of the diffe
On 12/21/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> robert burrell donkin wrote:
>> > On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> >> robert burrell donkin wrote:
>> >> > On 12/19/06, Steve Lo
robert burrell donkin wrote:
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> robert burrell donkin wrote:
>> > On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> 2. looking to get managemen
Carlos Sanchez wrote:
just some holiday fun ahead...
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> We are
>>
>> 1. planning an apache con EU talk, "fear the repository police".
>
> in suitable costumes, i hope ;-)
nothing planned, but if we have someone in the audience cued up to s
On 12/20/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
just some holiday fun ahead...
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
> >> We are
> >>
> >> 1. planning an apache con EU talk, "fear the repository police".
> >
> > in suitable costumes, i hope ;-)
>
> nothing planned, but if
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> robert burrell donkin wrote:
>> > On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> 2. looking to get management approval to hand the code t
just some holiday fun ahead...
On 12/20/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> We are
>>
>> 1. planning an apache con EU talk, "fear the repository police".
>
> in suitable costumes, i hope ;-)
nothing planned, but if we have someone in the audience cued up to say
"I didnt expect the
robert burrell donkin wrote:
On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
>
>
>> I'd like to see POM auditing in there somewhere.
>
> +1
>
> henri's been talking about adding this to RAT. IMHO this
On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
>
>
>> I'd like to see POM auditing in there somewhere.
>
> +1
>
> henri's been talking about adding this to RAT. IMHO this should be
> implemented as a
robert burrell donkin wrote:
On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
I'd like to see POM auditing in there somewhere.
+1
henri's been talking about adding this to RAT. IMHO this should be
implemented as a separate component so that it could be used by a
variety of applicatio
On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
I'd like to see POM auditing in there somewhere.
+1
henri's been talking about adding this to RAT. IMHO this should be
implemented as a separate component so that it could be used by a
variety of applications: for example, it might be i
On 12/19/06, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
Hello Joakim,
I like this discussion, I am a big fan of automating the release
process.
I also have some hands on experience being RM for Ant 1.6 and 1.7.
For Ant 1.7, we are using what you call the staged release process.
When I pr
Hello Joakim,
I like this discussion, I am a big fan of automating the release
process.
I also have some hands on experience being RM for Ant 1.6 and 1.7.
For Ant 1.7, we are using what you call the staged release process.
When I prepare a build, I have to assume that the vote on the
bina
Joakim Erdfelt wrote:
This is just a synopsis email about the future of the release process.
Disclaimer: I am not attempting to set policy, just to get discussion
going,
document it, and work towards the ideal toolchain that
make the
future of apache releases
Does this cover the whole topic?
http://docs.codehaus.org/display/MAVENUSER/BEA+Maven+Requirement
+Documents
I think it's all good - as long as it is all built on top of the
stuff we already have (including what Joakim is proposing). It will
probably require changes to many aspects of Maven
On 14/12/2006, at 10:46 AM, Joakim Erdfelt wrote:
* If unanimous +1 vote by 7 or more PMC members, then release
can occur before 72 hour window is up.
Don't really understand the rush, or the arbitrary number 7 (yes, it
is the number of perfection, but other than that, it has
On Wednesday 13 December 2006 18:46, Joakim Erdfelt wrote:
> Techniques:
> 2) Staged release process
> This process uses a staging workflow, there is no plugin for this
> process (yet).
>
> The benefits of this process is that a real binary is being blessed.
> This process als
On Wednesday 13 December 2006 18:54, Tom Huybrechts wrote:
> >6) All source files in the sources.jar files will contain the
> > following header.
> > ---(snip)---
> > Licensed to the Apache Software Foundation (ASF) under one
> > or more contributor license agreements. See th
Hi,
If I understand correctly, the problem is that a 'staged' release still
contains a SNAPSHOT keyword in the metadata/filename?
Also, how would you see snapshot 'releases' without a snapshot keyword?
If there's no indicator (timestamp?) in the filename, you'll overwrite the
previous deployed
On 12/14/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
On Thu, December 14, 2006 1:46 am, Joakim Erdfelt wrote:
> Disclaimer: I am not attempting to set policy, just to get discussion
> going,
> document it, and work towards the ideal toolchain that
> make the
> fut
On Thu, December 14, 2006 1:46 am, Joakim Erdfelt wrote:
> Disclaimer: I am not attempting to set policy, just to get discussion
> going,
> document it, and work towards the ideal toolchain that
> make the
> future of apache releases smooth, consistent, and resilient
Hi Dan,
I think what you are describing is what you do at your work place,
and I think it might be good if you could give us a full description
of your system for folks here to help them understand exactly what it
is you're talking about. I probably know a little more about it then
most h
Thanks for a great e-mail Joakim. I wanted to chime in with my two
cents...
(I've been off the radar for a couple of months while waiting for
permission to sign my ICLA; it's in now, and I'm now back to paying more
careful attention to this process... forgive me if some of this has
already been
Joakim Erdfelt wrote:
This is just a synopsis email about the future of the release process.
Disclaimer: I am not attempting to set policy, just to get discussion
going,
document it, and work towards the ideal toolchain that
make the
future of apache releases
6) All source files in the sources.jar files will contain the following
header.
---(snip)---
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional informatio
This is just a synopsis email about the future of the release process.
Disclaimer: I am not attempting to set policy, just to get discussion
going,
document it, and work towards the ideal toolchain that
make the
future of apache releases smooth, consistent, and
35 matches
Mail list logo