On Mon, May 2, 2016 at 1:50 PM, Andrew Wang wrote:
> Hi all,
>
> I wanted to confirm my version numbering plan for Hadoop 3.x. We had a
> related thread on this topic about a year ago, mostly focusing on the
> branch-2 maintenance releases:
>
> http://mail-archives.apache.org/mod_mbox/hadoop-commo
On Mon, May 2, 2016 at 2:00 PM, Roman Shaposhnik
wrote:
> On Mon, May 2, 2016 at 1:50 PM, Andrew Wang
> wrote:
> > Hi all,
> >
> > I wanted to confirm my version numbering plan for Hadoop 3.x. We had a
> > related thread on this topic about a year ago, mostly focusing on the
> > branch-2 mainten
nal Message-
From: Andrew Wang [mailto:andrew.w...@cloudera.com]
Sent: Tuesday, May 03, 2016 5:07 AM
To: Roman Shaposhnik
Cc: common-dev@hadoop.apache.org
Subject: Re: Release numbering for 3.x leading up to GA
On Mon, May 2, 2016 at 2:00 PM, Roman Shaposhnik
wrote:
> On Mon, May 2, 2
>
> >> but I'm going to spend time on our first RC this week.
> Sorry what does this mean? Did you mean the first RC version or
> 3.0.0-alpha1 will be cut out this week?
> Anyway will try to get some tasks done sooner.
>
> First RC for whatever we name the first 3.0 alpha release.
There's no need
Ok, got it. Thanks for the explanation.
Regards,
Kai
From: Andrew Wang [mailto:andrew.w...@cloudera.com]
Sent: Tuesday, May 03, 2016 5:41 AM
To: Zheng, Kai
Cc: common-dev@hadoop.apache.org
Subject: Re: Release numbering for 3.x leading up to GA
>> but I'm going to spend time on o
pache.org
> Subject: Re: Release numbering for 3.x leading up to GA
>
> >> but I'm going to spend time on our first RC this week.
> Sorry what does this mean? Did you mean the first RC version or
> 3.0.0-alpha1 will be cut out this week?
> Anyway will try to get some tas
On Tue, May 3, 2016 at 8:18 AM, Karthik Kambatla wrote:
> The naming scheme sounds good. Since we want to start out sooner, I am
> assuming we are not limiting ourselves to two alphas as the email might
> indicate.
>
> Also, as the release manager, can you elaborate on your definitions of
> alpha
Hi all,
Sounds like we have general agreement on this release numbering scheme for
3.x.
I'm going to attempt some mvn and JIRA invocations to get the version
numbers lined up for alpha1, wish me luck.
Best,
Andrew
On Tue, May 3, 2016 at 9:52 AM, Roman Shaposhnik
wrote:
> On Tue, May 3, 2016 a
Thanks Andrew for driving. Sounds good. Go ahead please.
Good luck :-)
Regards,
Uma
On 5/12/16, 10:52 AM, "Andrew Wang" wrote:
>Hi all,
>
>Sounds like we have general agreement on this release numbering scheme for
>3.x.
>
>I'm going to attempt some mvn and JIRA invocations to get the version
>
Hi folks,
I think it's working, though it takes some time for the rename to propagate
in JIRA. JIRA is also currently being hammered by spammers, which might be
related.
Anyway, the new "3.0.0-alpha1" version should be live for all four
subprojects, so have at it!
Best,
Andrew
On Thu, May 12, 2
Naming convention looks good. Thanks Andrew for driving this!
Could you explain a little more on the criteria of cutting alpha1 / alpha2?
What are the goals we want to achieve for alpha1? From EC's perspective,
maybe we should target on having all compatibility-related changes in
alpha1, like new
The sooner the better for incompatible changes, but at this point we are
explicitly not guaranteeing any compatibility between alpha releases.
For EC, my understanding is that we're still working on the coder
configuration. Given that we're still working on L&N changes, I think it's
possible that
Thanks Andrew. I also had a talk with Kai offline. Agreed that we should
try our best to finalize coder config changes for alpha1.
On Tue, May 17, 2016 at 5:34 PM Andrew Wang
wrote:
> The sooner the better for incompatible changes, but at this point we are
> explicitly not guaranteeing any compa
: Andrew Wang
Cc: Gangumalla, Uma ; Roman Shaposhnik
; Karthik Kambatla ;
common-dev@hadoop.apache.org
Subject: Re: Release numbering for 3.x leading up to GA
Thanks Andrew. I also had a talk with Kai offline. Agreed that we should try
our best to finalize coder config changes for alpha1.
On Tue
14 matches
Mail list logo