[jira] [Created] (HADOOP-9280) HADOOP-7101 was never merged from 0.2.x to the 1.x branch

2013-02-04 Thread Claus Ibsen (JIRA)
Claus Ibsen created HADOOP-9280: --- Summary: HADOOP-7101 was never merged from 0.2.x to the 1.x branch Key: HADOOP-9280 URL: https://issues.apache.org/jira/browse/HADOOP-9280 Project: Hadoop Common

[jira] [Created] (HADOOP-9279) Compile failure when hadoop-maven-plugins doesn't exist in local repository

2013-02-04 Thread Tsuyoshi OZAWA (JIRA)
Tsuyoshi OZAWA created HADOOP-9279: -- Summary: Compile failure when hadoop-maven-plugins doesn't exist in local repository Key: HADOOP-9279 URL: https://issues.apache.org/jira/browse/HADOOP-9279 Proje

Re: Release numbering for branch-2 releases

2013-02-04 Thread Steve Loughran
disclaimer, personal opinions only, I just can't be bothered to subscribe with @apache.org right now. On 4 February 2013 14:36, Todd Lipcon wrote: > - Quality/completeness: for example, missing docs, buggy UIs, difficult > setup/install, etc > par for the course. Have you ever used Linux? > -

Re: [PROPOSAL] Hadoop branch-1.2

2013-02-04 Thread Steve Loughran
I've been working on some stricter contract tests for filesystems, and have some changes for S3 and S3N that we've been working through. While this is mostly minor, rename(dir,dir/subdir) can lose all data in the source directory https://issues.apache.org/jira/browse/HADOOP-9261 I think that shou

[jira] [Created] (HADOOP-9278) TestHarFileSystemBasics fails on Windows due to invalid HAR URI and file handle leak

2013-02-04 Thread Chris Nauroth (JIRA)
Chris Nauroth created HADOOP-9278: - Summary: TestHarFileSystemBasics fails on Windows due to invalid HAR URI and file handle leak Key: HADOOP-9278 URL: https://issues.apache.org/jira/browse/HADOOP-9278

[jira] [Created] (HADOOP-9277) Improve javadoc for FileContext

2013-02-04 Thread Andrew Wang (JIRA)
Andrew Wang created HADOOP-9277: --- Summary: Improve javadoc for FileContext Key: HADOOP-9277 URL: https://issues.apache.org/jira/browse/HADOOP-9277 Project: Hadoop Common Issue Type: Improvement

Re: Release numbering for branch-2 releases

2013-02-04 Thread Todd Lipcon
On Mon, Feb 4, 2013 at 2:14 PM, Suresh Srinivas wrote: > > Why? Can you please share some reasons? > > I actually think alpha and beta and stable/GA are much better way to set > the expectation > of the quality of a release. This has been practiced in software release > cycle for a long time. > Ha

Re: Release numbering for branch-2 releases

2013-02-04 Thread Suresh Srinivas
On Mon, Feb 4, 2013 at 1:07 PM, Owen O'Malley wrote: > I think that using "-(alpha,beta)" tags on the release versions is a really > bad idea. Why? Can you please share some reasons? I actually think alpha and beta and stable/GA are much better way to set the expectation of the quality of a re

Re: Release numbering for branch-2 releases

2013-02-04 Thread Owen O'Malley
I think that using "-(alpha,beta)" tags on the release versions is a really bad idea. All releases should follow the strictly numeric (Major.Minor.Patch) pattern that we've used for all of the releases except the 2.0.x ones. -- Owen On Mon, Feb 4, 2013 at 11:53 AM, Stack wrote: > On Mon, Feb 4

[PROPOSAL] Hadoop branch-1.2

2013-02-04 Thread Matt Foley
Hi, this weekend I propose to create a branch-1.2 from current branch-1, and create a first release candidate. There's a ton of new stuff since 1.1, and it will probably need stabilization, but that is best done in the context of a release candidate. Any objections? Any must-have items for 1.2 t

Re: Release numbering for branch-2 releases

2013-02-04 Thread Stack
On Mon, Feb 4, 2013 at 10:46 AM, Arun C Murthy wrote: > Would it better to have 2.0.3-alpha, 2.0.4-beta and then make 2.1 as a > stable release? This way we just have one series (2.0.x) which is not > suitable for general consumption. > > That contains the versioning damage to the 2.0.x set. Th

Re: Release numbering for branch-2 releases

2013-02-04 Thread Suresh Srinivas
On Mon, Feb 4, 2013 at 10:46 AM, Arun C Murthy wrote: > > On Feb 1, 2013, at 2:34 AM, Tom White wrote: > > Whereas Arun is proposing > > > > 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.1.0-alpha, 2.2.0-beta, 2.3.0 > > > > and the casual observer might expect there to be a stable 2.0.1 (say) > > on

Re: Release numbering for branch-2 releases

2013-02-04 Thread Arun C Murthy
On Feb 1, 2013, at 2:34 AM, Tom White wrote: > Whereas Arun is proposing > > 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.1.0-alpha, 2.2.0-beta, 2.3.0 > > and the casual observer might expect there to be a stable 2.0.1 (say) > on seeing the existence of 2.0.2-alpha. > > The first three of these ar

[jira] [Resolved] (HADOOP-9052) fix 6 failing tests in hadoop-streaming

2013-02-04 Thread Robert Joseph Evans (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved HADOOP-9052. - Resolution: Duplicate > fix 6 failing tests in hadoop-streaming > --

[jira] [Reopened] (HADOOP-9052) fix 6 failing tests in hadoop-streaming

2013-02-04 Thread Robert Joseph Evans (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reopened HADOOP-9052: - Reopening to resolve as a duplicate. > fix 6 failing tests in hadoo

Re: Help to setup latest Hadoop source code on Eclipse

2013-02-04 Thread Karthiek C
Thanks Erik. I am now trying to set up 1.1 version that uses ANT. Will use your tip when I start working with latest version. On Mon, Feb 4, 2013 at 9:00 AM, Erik Paulson wrote: > I found that I needed to add the M2 Repo to the Eclipse classpath settings > in order to get a successful build. Th

Re: Help to setup latest Hadoop source code on Eclipse

2013-02-04 Thread Erik Paulson
I found that I needed to add the M2 Repo to the Eclipse classpath settings in order to get a successful build. This page details several different ways to accomplish that: http://www.mkyong.com/maven/how-to-configure-m2_repo-variable-in-eclipse-ide/ -Erik On Fri, Feb 1, 2013 at 8:44 AM, Karthie