On Fri, Nov 27, 2009 at 3:42 PM, Brett Porter wrote:
> Brian,
>
> I'm not sure if you were replying to me or others, but you quoted me and
> snipped my actual point:
>
> "I'm fine with either more or less frequent releases... I'm not fine with
> circumventing review or pushing releases outside t
Brian,
I'm not sure if you were replying to me or others, but you quoted me and
snipped my actual point:
"I'm fine with either more or less frequent releases... I'm not fine with
circumventing review or pushing releases outside the ASF."
I agree with everything you said below. I was saying we
> I'm also not pushing for duration for "testing" purposes. That's part of it,
> but as Jason said
>automation can reduce the need over time (though it's never going to be 100%
>so there's some value
>in testing). However, it is mostly for an opportunity to review changes. If we
>do "8 releases
On 27/11/2009, at 2:27 AM, Todd Thiessen wrote:
>> The logic here is flawed because it is from a single
>> perspective of an
>> individual who finds it burdensome to validate each and every release.
>
> It isn't just me. Both Paul and Brett expressed similar concerns ;-).
I don't think this
On 2009-11-26, at 11:23 AM, Ralph Goers wrote:
On Nov 26, 2009, at 5:56 AM, Jason van Zyl wrote:
On 2009-11-26, at 8:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here
internally but I can also attest that releasing too often is a
real pain. You en
On 2009-11-26, at 11:04 AM, Ralph Goers wrote:
On Nov 26, 2009, at 5:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here
internally but I can also attest that releasing too often is a real
pain. You end up having a bunch of releases publicized that no
On Nov 26, 2009, at 5:56 AM, Jason van Zyl wrote:
>
> On 2009-11-26, at 8:04 AM, Todd Thiessen wrote:
>
>> I can only speak from experience with what we have done here internally but
>> I can also attest that releasing too often is a real pain. You end up having
>> a bunch of releases publici
On Nov 26, 2009, at 5:04 AM, Todd Thiessen wrote:
> I can only speak from experience with what we have done here internally but I
> can also attest that releasing too often is a real pain. You end up having a
> bunch of releases publicized that no one cares about. It only serves to
> clutter a
s.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Wednesday, November 25, 2009 9:21 PM
To: Maven Developers List
Subject: Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
I would also like to contribute my frustration with the
current build process. It's great the alpha releases
ying to evaluate 3.x.
>
> > ---
> > Todd Thiessen
> >
> >
> >> -Original Message-
> >> From: paulus.benedic...@gmail.com
> >> [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
> >> Sent: Wednesday, November 25, 20
s.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Wednesday, November 25, 2009 9:21 PM
To: Maven Developers List
Subject: Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
I would also like to contribute my frustration with the
current build process.
> -Original Message-
> From: paulus.benedic...@gmail.com
> [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
> Sent: Wednesday, November 25, 2009 9:21 PM
> To: Maven Developers List
> Subject: Re: voting was: [VOTE] Release Apache Maven 3.0-alpha-5
>
2009/11/26 Paul Benedict :
> I would also like to contribute my frustration with the current build
> process. It's great the alpha releases are coming out often, but I
> cannot possibly be testing them at the frequency you guys are
> currently tagging and voting. I thought the "once a week" alpha w
I would also like to contribute my frustration with the current build
process. It's great the alpha releases are coming out often, but I
cannot possibly be testing them at the frequency you guys are
currently tagging and voting. I thought the "once a week" alpha was a
good idea until it actually ha
Let's not beat the dead horse. No one cares. There's not good reason
for not releasing something immediately if there are fixes available.
That's just not the way it works here, that's fine and not a big deal.
On 2009-11-25, at 7:52 PM, Brett Porter wrote:
On 26/11/2009, at 6:24 AM, Jason
On 26/11/2009, at 6:24 AM, Jason van Zyl wrote:
> If ever we really needed to push out builds more frequently I would just do
> it from Sonatype. I've given up trying to be truly agile at Apache, it's just
> not going to happen.
I don't understand what the issue is with the current process. Be
If ever we really needed to push out builds more frequently I would
just do it from Sonatype. I've given up trying to be truly agile at
Apache, it's just not going to happen.
On 2009-11-25, at 2:10 PM, Dan Fabulich wrote:
Niall Pemberton wrote:
On Mon, Nov 23, 2009 at 7:59 PM, Paul Gier
Niall Pemberton wrote:
On Mon, Nov 23, 2009 at 7:59 PM, Paul Gier wrote:
I wonder if we really need a full vote for every alpha. Especially if this
is going to happen every two weeks. Why not just vote for a 2 week alpha
release schedule and then don't do another vote until it's time for bet
18 matches
Mail list logo