Hi Waldyn,
I'm about to put out a Hadoop 1.2.1 release candidate, within the next day
or so, which will hopefully be accepted as the new stable release. Then
I'll do a 1.3.0 from current branch-1, which will become the new beta.
Thanks,
--Matt
On Thu, Jul 18, 2013 at 8:29 AM, Benbenek, Waldyn
Greetings,
Hadoop 1.2.0 is listed as a beta release. Is there any idea as to when an
official ( that is, non-beta) release is scheduled.
Thanks,
Wally Benbenek
On Feb 19, 2010, at 3:14 PM, Eli Collins wrote:
On Fri, Feb 19, 2010 at 2:49 PM, Doug Cutting cutt...@apache.org
wrote:
Eli Collins wrote:
My concern is more about when the next branch from trunk will be
made.
Does there need to be a dependency?
No. I just wanted to note that, from
Sanjay Radia wrote:
Rather than renaming versions, lets vote on the compatibility rules for
22: 22 is API compatible with 20.
I think if we elect to go this way then we should make the rule more
general, i.e.: all releases after 0.20 are to be API-compatible with
0.20 until we state
: maandag 22 februari 2010 5:55
To: general@hadoop.apache.org
Cc: general@hadoop.apache.org
Subject: Re: Release plans
Well, since someone has to get the ball rolling as far as release
masters, I'll nominate Stack and/or someone hbase related for 0.21
with the primary goal of being soon
to roll out in March.
Where can I find information about this?
Best regards,
Evert Lammerts
-Original Message-
From: Jay Booth [mailto:jaybo...@gmail.com]
Sent: maandag 22 februari 2010 5:55
To: general@hadoop.apache.org
Cc: general@hadoop.apache.org
Subject: Re: Release plans
Evert Lammerts wrote:
I'm sorry for breaking into your discussion as an outsider, but I'm
very
curious about the security features you are planning to roll out in
March.
At a high level, all of the interactions with HDFS and MapReduce will
be authenticated. Kerberos will be used as the
Well, since someone has to get the ball rolling as far as release
masters, I'll nominate Stack and/or someone hbase related for 0.21
with the primary goal of being soon? They get a big win from append
and others will gain from the expanded mapreduce lib, better
schedulers, etc. There are
On Fri, Feb 19, 2010 at 4:23 PM, Eli Collins e...@cloudera.com wrote:
Can we make a decision on basing 21 on the current branch and if it's
decided that 22 can't remove stuff that was in 20 we'll go back and do
the necessary additions on 21 and trunk? Suspect that decision will
take a lot more
On Thu, Feb 18, 2010 at 8:36 PM, Stack st...@duboce.net wrote:
On Thu, Feb 18, 2010 at 5:02 PM, Owen O'Malley omal...@apache.org wrote:
Yahoo doesn't care. Even if we rebase the 0.21 branch, because of the
timing, Yahoo will probably never deploy it. (It take months to push a
release through
+1 from me.
I agree with Stack; faster release cycles will help keep the project focused
and get code testing and soaking in more environments.
- Aaron
On Fri, Feb 19, 2010 at 1:44 PM, Eli Collins e...@cloudera.com wrote:
On Thu, Feb 18, 2010 at 8:36 PM, Stack st...@duboce.net wrote:
On
Eli Collins wrote:
Given that Yahoo and others plan to skip 21, and the HBase crowd could
actually use 21 and have invested in the current branch's contents, it
sounds like we should try to get the current branch released.
My concern is more about when the next branch from trunk will be made.
Eli Collins wrote:
My concern is more about when the next branch from trunk will be made.
Does there need to be a dependency?
No. I just wanted to note that, from my point of view, releasing from
the existing 0.21 branch is not sufficient, that, regardless, we still
need to release from
On Fri, Feb 19, 2010 at 2:49 PM, Doug Cutting cutt...@apache.org wrote:
Eli Collins wrote:
My concern is more about when the next branch from trunk will be made.
Does there need to be a dependency?
No. I just wanted to note that, from my point of view, releasing from the
existing 0.21
On Fri, Feb 19, 2010 at 3:38 PM, Doug Cutting cutt...@apache.org wrote:
Eli Collins wrote:
Maybe we could get 21 behind
us and have a separate discussion covering those.
I'm personally more interested in that discussion than in what's currently
in the 0.21 branch, but others, like Stack,
On Tue, Feb 16, 2010 at 2:12 PM, Eli Collins e...@cloudera.com wrote:
Hey guys,
What are the current plans for the 21 release?
Doesn't seem like there is much interest going by the deafening silence Eli.
Did it come up last night at the HUG?
The roadmap on the wiki [1] says minor releases
On Thu, Feb 18, 2010 at 10:54 AM, Stack st...@duboce.net wrote:
On Tue, Feb 16, 2010 at 2:12 PM, Eli Collins e...@cloudera.com wrote:
Hey guys,
What are the current plans for the 21 release?
Doesn't seem like there is much interest going by the deafening silence Eli.
Did it come up last
Eli Collins wrote:
What are the current plans for the 21 release?
Personally, I'd rather re-branch 21 from trunk in early March. I
believe Y!'s security changes will be feature-complete in trunk by then.
Symlinks and end-to-end Avro should also hopefully be committed by then.
I'd then
On 2/18/10 11:29 AM, Doug Cutting cutt...@apache.org wrote:
Eli Collins wrote:
What are the current plans for the 21 release?
Personally, I'd rather re-branch 21 from trunk in early March. I
believe Y!'s security changes will be feature-complete in trunk by then.
Symlinks and
On Feb 18, 2010, at 11:29 AM, Doug Cutting wrote:
My presentation basically said that:
* Yahoo is currently running Yahoo's 0.20.8 on all 25,000 of our
nodes.
* We have made substantial numbers of feature back ports from trunk
into our branch. Including:
* improved Capacity
* Someone outside of Yahoo needs to step up and start addressing the
blockers to get 0.21 released.
Thanks for the update on the state of the world at Yahoo!, Owen--very
helpful. I think the community will step up to knock down some of the
blockers once we resolve what should be in the 0.21
Owen O'Malley wrote:
Rather than set a date, I think it is time to move to feature-based
releases.
The problem with feature-based releases is that one feature can delay
releases arbitrarily, so a single feature can hold all others hostage.
Rather I think we need to be willing to remove or
On Feb 18, 2010, at 3:06 PM, Jeff Hammerbacher wrote:
I think the community will step up to knock down some of the
blockers once we resolve what should be in the 0.21 release: the
current
branch, or a rebase on trunk. Do you/Yahoo! have a preference on
that front?
Yahoo doesn't care. Even
Thanks Owen, that's useful information. It sounds like the API
incompatibility vote can be a separate issue.
Do we have consensus around rebasing on 0.21? Anyone already testing on 0.21
who would be upset if the current branch were to be retired?
On Thu, Feb 18, 2010 at 5:02 PM, Owen O'Malley
On Thu, Feb 18, 2010 at 5:19 PM, Jeff Hammerbacher ham...@cloudera.com wrote:
Thanks Owen, that's useful information. It sounds like the API
incompatibility vote can be a separate issue.
Do we have consensus around rebasing on 0.21? Anyone already testing on 0.21
who would be upset if the
Todd Lipcon wrote:
One question I have is what to do with the JIRA tickets - we probably
need some kind of bulk edit, right? Anything that's currently resolved
with fix version 22 needs to be changed over to fix version 21?
Yes, that should be done if we decide to rebase the 0.21 branch.
Doug
On 2/18/2010 5:19 PM, Jeff Hammerbacher wrote:
Do we have consensus around rebasing on 0.21? Anyone already testing on 0.21
who would be upset if the current branch were to be retired?
Rebasing 0.21 will further delay the release.
In current 0.21 branch there is some 28 blockers,
which will
On Thu, Feb 18, 2010 at 6:08 PM, Konstantin Shvachko s...@yahoo-inc.com wrote:
On 2/18/2010 5:19 PM, Jeff Hammerbacher wrote:
Do we have consensus around rebasing on 0.21? Anyone already testing on
0.21
who would be upset if the current branch were to be retired?
Rebasing 0.21 will further
If we include symlinks, security and Avro in 0.21, then what's the feature
set for 0.22? Do we have any big items planned?
Thanks,
Tomer
On Thu, Feb 18, 2010 at 6:12 PM, Todd Lipcon t...@cloudera.com wrote:
On Thu, Feb 18, 2010 at 6:08 PM, Konstantin Shvachko s...@yahoo-inc.com
wrote:
On
On Thu, Feb 18, 2010 at 5:02 PM, Owen O'Malley omal...@apache.org wrote:
Yahoo doesn't care. Even if we rebase the 0.21 branch, because of the
timing, Yahoo will probably never deploy it. (It take months to push a
release through QA and production testing, as I wrote the security release
will
Hey guys,
What are the current plans for the 21 release?
The roadmap on the wiki [1] says minor releases are made regularly,
every few months. The 21 branch was created 5 months ago, and the
release dates in jira for the various core projects have all passed. I
know some projects, eg HBase,
31 matches
Mail list logo
