Releases table needs to be cleaned up

Hi folks, https://hadoop.apache.org/releases.html The table of releases here is supposed to only contain one row per release line. We've got a lot of old dupes at this point, e.g. 3.0.2, 2.9.0, 2.8.3. It'd also be good to keep this sorted by version number, so 3.1.0 is at the top. Could a

Re: site doc cleanup

It seems aggressive to delete docs just because a line hasn't had a recent release. We don't have a formal EOL policy for release lines, and old releases (particularly old clients) are still used and old docs linked in places. Also, sorry if I missed the original rationale, but what do we gain

Re: HADOOP-15124 review

I think it's fine to ask for review help on the dev list, sometimes JIRAs are missed or get stuck. It also helps sometimes to git blame the files you're touching and see who is a likely reviewer, and then pinging them on JIRA to ask for a review. Igor, hopefully a committer takes interest in your

Re: [VOTE] Merging branch HDFS-7240 to trunk

Hi Sanjay, thanks for the response, replying inline: - NN on top HDSL where the NN uses the new block layer (Both Daryn and Owen > acknowledge the benefit of the new block layer). We have two choices here > ** a) Evolve NN so that it can interact with both old and new block layer, > ** b)

Re: [VOTE] Merging branch HDFS-7240 to trunk

On Fri, Mar 2, 2018 at 4:24 PM, Owen O'Malley <owen.omal...@gmail.com> > wrote: > >> On Thu, Mar 1, 2018 at 11:03 PM, Andrew Wang <andrew.w...@cloudera.com> >> wrote: >> >> Owen mentioned making a Hadoop subproject; we'd have to >> > hash out what exactl

Re: [VOTE] Merging branch HDFS-7240 to trunk

Hi Sanjay, I have different opinions about what's important and how to eventually integrate this code, and that's not because I'm "conveniently ignoring" your responses. I'm also not making some of the arguments you claim I am making. Attacking arguments I'm not making is not going to change my

Re: [VOTE] Merging branch HDFS-7240 to trunk

pluggable. At that point (likely in the Hadoop 4 timeframe), we'll be ready to pursue HDFS-on-HDSL integration. Best, Andrew On Tue, Feb 27, 2018 at 11:23 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: > > > > > > > > > > *Hi Jitendra and all,Thanks for putting

Re: [VOTE] Merging branch HDFS-7240 to trunk

*Hi Jitendra and all,Thanks for putting this together. I caught up on the discussion on JIRA and document at HDFS-10419, and still have the same concerns raised earlier

Re: [DISCUSS] 2.9+ stabilization branch

3. > GPU support would be a serious catalyst for us to move forward, which I > also heard from other organizations interested in ML. > > Thanks, > --Konstantin > > On Tue, Feb 27, 2018 at 1:28 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > >> Hi Arun

Re: [DISCUSS] 2.9+ stabilization branch

Hi Arun/Subru, Bumping the minimum Java version is a major change, and incompatible for users who are unable to upgrade their JVM version. We're beyond the EOL for Java 7, but as we know from our experience with Java 6, there are plenty of users who stick on old Java versions. Bumping the Java

Re: Apache Hadoop 3.0.1 Release plan

Hi Eddy, thanks for taking this on, Historically we've waited for the first RC to cut the release branch since it keeps things simpler for committers. Also, could you check the permissions on your JIRA filter? It shows as private for me. Best, Andrew On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

ot; to match > the pattern for prior releases. > > Thanks, > Jonathan Kelly > > On Thu, Dec 14, 2017 at 10:45 AM Andrew Wang <andrew.w...@cloudera.com> > wrote: > >> Hi all, >> >> I'm pleased to announce that Apache Hadoop 3.0.0 is generally available >

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

pit Agarwal <aagar...@hortonworks.com> wrote: > That makes sense for Beta users but most of our users will be upgrading > from a previous GA release and the changelog will mislead them. The webpage > does not mention this is a delta from the beta release. > > > > > > *Fr

Re: Missing some trunk commit history

We actually already did: https://lists.apache.org/thread.html/43cd65c6b6c3c0e8ac2b3c76afd9eff1f78b177fabe9c4a96d9b3d0b@1440189889@%3Ccommon-dev.hadoop.apache.org%3E On Fri, Dec 15, 2017 at 10:54 AM, Eric Yang wrote: > +1 for merge –no-ff for feature merge. > Do we all

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

t; I assume you only counted 3.0.0 changes in this log excluding > alphas/betas. However, users shouldn’t have to manually compile > incompatibilities by summing up a/b release notes. Can we fix the changelog > after the fact? > > > > > On 12/14/17, 10:45 AM, "Andrew Wang

[ANNOUNCE] Apache Hadoop 3.0.0 GA is released

Hi all, I'm pleased to announce that Apache Hadoop 3.0.0 is generally available (GA). 3.0.0 GA consists of 302 bug fixes, improvements, and other enhancements since 3.0.0-beta1. This release marks a point of quality and stability for the 3.0.0 release line, and users of earlier 3.0.0-alpha and

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

release. > > > > > > Thanks, > > > > Junping > > > > > > From: Robert Kanter <rkan...@cloudera.com> > > Sent: Tuesday, December 12, 2017 3:10 PM > > To: Arun Suresh > > Cc: Andrew Wang;

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

get/cat on "/" with XOR-2-1 policy. > > Thanks Andrew for this great effort! > > Best, > > > On Tue, Dec 12, 2017 at 9:55 AM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > > Hi Wei-Chiu, > > > > The patchprocess directory is left ove

[jira] [Created] (HADOOP-15112) create-release didn't sign artifacts

Andrew Wang created HADOOP-15112: Summary: create-release didn't sign artifacts Key: HADOOP-15112 URL: https://issues.apache.org/jira/browse/HADOOP-15112 Project: Hadoop Common Issue Type

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

nitpicking, but you might want to double check so we don't > ship anything private to you in public :) > > > > On Tue, Dec 12, 2017 at 7:48 AM, Ajay Kumar <ajay.ku...@hortonworks.com> > wrote: > >> +1 (non-binding) >> Thanks for driving this, Andrew Wang!! >&g

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

ss > because of the mutability of tags. > > On Mon, Dec 11, 2017 at 10:31 AM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > >> Sorry, forgot to push the tag. It's up there now. >> >> On Sun, Dec 10, 2017 at 8:31 PM, Vinod Kumar Vavilapalli < >> vino...@apach

[VOTE] Release Apache Hadoop 3.0.0 RC1

Hi all, Let me start, as always, by thanking the efforts of all the contributors who contributed to this release, especially those who jumped on the issues found in RC0. I've prepared RC1 for Apache Hadoop 3.0.0. This release incorporates 302 fixed JIRAs since the previous 3.0.0-beta1 release.

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

FYI that we got our last blocker in today, so I'm currently rolling RC1. Stay tuned! On Thu, Nov 30, 2017 at 8:32 AM, Allen Wittenauer wrote: > > > On Nov 30, 2017, at 1:07 AM, Rohith Sharma K S < > rohithsharm...@apache.org> wrote: > > > > > > >. If ATSv1 isn’t

2017-12-01 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-12-01 Haven't written one of these in a month. I had high hopes for RC0, but it failed due to HADOOP-15058 - create-release site build

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Hi folks, Thanks again for the testing help with the RC. Here's our dashboard for the 3.0.0 release: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329849 Right now we're tracking three blockers: * HADOOP-15058 is the create-release fix, I just put up a patch which needs

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

On Mon, Nov 20, 2017 at 11:33 PM, Allen Wittenauer wrote: > > The original release script and instructions broke the build up > into three or so steps. When I rewrote it, I kept that same model. It’s > probably time to re-think that. In particular, it should

[jira] [Created] (HADOOP-15058) create-release site build outputs dummy shaded jars due to skipShade

Andrew Wang created HADOOP-15058: Summary: create-release site build outputs dummy shaded jars due to skipShade Key: HADOOP-15058 URL: https://issues.apache.org/jira/browse/HADOOP-15058 Project

Re: Apache Hadoop 2.8.3 Release Plan

gt; > Pls let me know what you think. Thanks! > > > > Thanks, > > > Junping > > > -- > *From:* Andrew Wang <andrew.w...@cloudera.com> > *Sent:* Monday, November 20, 2017 10:22 PM > *To:* Zheng, Kai > *Cc:* Junping Du

Re: Apache Hadoop 2.8.3 Release Plan

> > > >> If we're struggling with being able to deliver new features in a safe > and timely fashion, let's try to address that... > > This is interesting. Do you aware any means to do that? Thanks! > > I've mentioned this a few times on the lists before, but our biggest gap in keeping branches

Re: Apache Hadoop 2.8.3 Release Plan

I'm against including new features in maintenance releases, since they're meant to be bug-fix only. If we're struggling with being able to deliver new features in a safe and timely fashion, let's try to address that, not overload the meaning of "maintenance release". Best, Andrew On Mon, Nov

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

On Mon, Nov 20, 2017 at 9:59 PM, Sangjin Lee <sj...@apache.org> wrote: > > On Mon, Nov 20, 2017 at 9:46 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > >> Thanks for the spot Sangjin. I think this bug introduced in >> create-release by HADOOP-14835.

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Thanks for the thorough review Vinod, some inline responses: *Issues found during testing* > > Major > - The previously supported way of being able to use different tar-balls > for different sub-modules is completely broken - common and HDFS tar.gz are > completely empty. > Is this something

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

;> for every new 'mvn install' even though there are no source changes - we >>> should see how this can be avoided. >>> - Compatibility notes >>> -- NM's env list is curtailed unlike in 2.x (For e.g, >>> HADOOP_MAPRED_HOME is not automatically inherited. Correct

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

? It would be a courtesy to our broader > community and I see no harm in giving everyone a few days to evaluate it > more thoroughly. > > On a lighter note, your deadline is also 4 minutes short of the required 5 > days. :) > > Regards, > Arpit > > > > On 11/14/17

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

> Thanks, > Akira > > > On 2017/11/15 6:34, Andrew Wang wrote: > >> Hi folks, >> >> Thanks as always to the many, many contributors who helped with this >> release. I've created RC0 for Apache Hadoop 3.0.0. The artifacts are >> available here: >> >

Re: [DISCUSS] A final minor release off branch-2?

Hi Junping, On Wed, Nov 15, 2017 at 1:37 AM, Junping Du wrote: > Thanks Vinod to bring up this discussion, which is just in time. > > I agree with most responses that option C is not a good choice as our > community bandwidth is precious and we should focus on very limited

Re: [DISCUSS] A final minor release off branch-2?

To follow up on my earlier email, I don't think there's need for a bridge release given that we've successfully tested rolling upgrade from 2.x to 3.0.0. I expect we'll keep making improvements to smooth over any additional incompatibilities found, but there isn't a requirement that a user upgrade

[VOTE] Release Apache Hadoop 3.0.0 RC0

Hi folks, Thanks as always to the many, many contributors who helped with this release. I've created RC0 for Apache Hadoop 3.0.0. The artifacts are available here: http://people.apache.org/~wang/3.0.0-RC0/ This vote will run 5 days, ending on Nov 19th at 1:30pm Pacific. 3.0.0 GA contains 291

Re: Heads up: branching branch-3.0.0 for GA

Branching is complete. Please use the 3.0.1 fix version for further commits to branch-3.0. Ping me if you want something in branch-3.0.0 since I'm rolling RC0 now. On Tue, Nov 14, 2017 at 11:08 AM, Andrew Wang <andrew.w...@cloudera.com> wrote: > Hi folks, > > We've resolved a

Heads up: branching branch-3.0.0 for GA

Hi folks, We've resolved all the blockers for 3.0.0 and the release notes and changelog look good, so I'm going to cut the branch and get started on the RC. * branch-3.0 will advance to 3.0.1-SNAPSHOT * branch-3.0.0 will go to 3.0.0 Please keep this in mind when committing. Cheers, Andrew

[jira] [Created] (HADOOP-15037) Add site release notes for OrgQueue and resource types

Andrew Wang created HADOOP-15037: Summary: Add site release notes for OrgQueue and resource types Key: HADOOP-15037 URL: https://issues.apache.org/jira/browse/HADOOP-15037 Project: Hadoop Common

Re: [DISCUSS] A final minor release off branch-2?

What are the known gaps that need bridging between 2.x and 3.x? >From an HDFS perspective, we've tested wire compat, rolling upgrade, and rollback. >From a YARN perspective, we've tested wire compat and rolling upgrade. Arun just mentioned an NM rollback issue that I'm not familiar with.

[jira] [Created] (HADOOP-15018) Update JAVA_HOME in create-release for Xenial Dockerfile

Andrew Wang created HADOOP-15018: Summary: Update JAVA_HOME in create-release for Xenial Dockerfile Key: HADOOP-15018 URL: https://issues.apache.org/jira/browse/HADOOP-15018 Project: Hadoop Common

2017-10-31 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+ updates 2017-10-31 Lots of progress towards GA, we look on track for cutting RC0 this week. I ran the versions script to check the branch matches up with JIRA and fixed things up, and also checked that the changelog and

[jira] [Resolved] (HADOOP-14555) document how to run wasb tests in azure docs site/testing.md

[ https://issues.apache.org/jira/browse/HADOOP-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-14555. -- Resolution: Duplicate Fix Version/s: (was: 3.0.0) > document how to run wasb te

[jira] [Reopened] (HADOOP-14555) document how to run wasb tests in azure docs site/testing.md

[ https://issues.apache.org/jira/browse/HADOOP-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14555: -- > document how to run wasb tests in azure docs site/testing

Re: Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

FWIW we've been running branch-3.0 unit tests successfully internally, though we have separate jobs for Common, HDFS, YARN, and MR. The failures here are probably a property of running everything in the same JVM, which I've found problematic in the past due to OOMs. On Tue, Oct 24, 2017 at 4:04

2017-10-20 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-10-20 Apologies for skipping the update last week. Here's how we're tracking for GA. Highlights: - Merge of HDFS router-based federation and API-based scheduler configuration with no reported

Re: 2017-10-06 Hadoop 3 release status update

On Oct 6, 2017, at 1:31 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > > > > - Still waiting on Allen to review YARN native services feature. > > Fake news. > > I’m still -1 on it, at least prior to a patch that posted late > yesterday. I’l

2017-10-06 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-10-06 The beta1 RC0 vote passed, and beta1 is out! Now tracking GA features. Highlights: - 3.0.0-beta1 has been released! - Router-based federation merge vote should be about to pass - API-based

Re: [VOTE] Release Apache Hadoop 3.0.0-beta1 RC0

M HA/work-preservring-restart/ NM-work-preserving restart > for ATSv2 entities. > - verified all ATSv2 REST end points to retrieve the entities > - ran sample MR jobs and distributed jobs > > Thanks & Regards > Rohith Sharma K S > > On 4 October 2017 at 05:31, Andrew W

[ANNOUNCE] Apache Hadoop 3.0.0-beta1 has been released

Hi all, I'm pleased to announce the release of Apache Hadoop 3.0.0-beta1. This is our first beta release in the 3.0.0 release line, and is planned to be the last release before 3.0.0 GA. Beta releases are API stable but come with no guarantee of quality, and are not intended for production use.

Re: [VOTE] Release Apache Hadoop 3.0.0-beta1 RC0

Connecting to >> > > https://localhost:14000/logLevel?log=org.apache.hadoop.fs. >> http.server. >> > HttpFSServer >> > >Exception in thread "main" >> > > org.apache.hadoop.security.authentication.client. >>

Re: [VOTE] Release Apache Hadoop 3.0.0-beta1 RC0

, Brahma Reddy Battula <bra...@apache.org> wrote: > > Thanks Andrew. > > +1 (non binding) > > --Built from source > --installed 3 node HA cluster > --Verified shell commands and UI > --Ran wordcount/pic jobs > > > > > On Fri, 29 Sep 2017 at 5:34 AM

2017-09-20 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-09-29 After about a month of slip, RC0 has been sent out for a VOTE. Focus now turns to GA, where we will attempt to keep the original beta1 target date (early November). Highlights: - RC0 vote was sent

Re: [DISCUSS] HADOOP-9122 Add power mock library for writing better unit tests

Making code testable is about a lot more than your mocking library. In HDFS, the NameNode is very monolithic, so it's hard to instantiate little pieces of functionality in isolation and mock things out. I have my doubts that Powermock will help with this unless someone's willing to invest in

Re: [DISCUSS] Merging API-based scheduler configuration to trunk/branch-2

Hi Jonathan, I'm okay with putting this into branch-3.0 for GA if it can be merged within the next two weeks. Even though beta1 has slipped by a month, I want to stick to the targeted GA data of Nov 1st as much as possible. Of course, let's not sacrifice quality or stability for speed; if

[VOTE] Release Apache Hadoop 3.0.0-beta1 RC0

Hi all, Let me start, as always, by thanking the many, many contributors who helped with this release! I've prepared an RC0 for 3.0.0-beta1: http://home.apache.org/~wang/3.0.0-beta1-RC0/ This vote will run five days, ending on Nov 3rd at 5PM Pacific. beta1 contains 576 fixed JIRA issues

Re: Heads up: branching branch-3.0.0-beta1 off of branch-3.0

Branch has been cut, branch-3.0 is now open for commits for 3.0.0 GA. HEAD of branch-3.0.0-beta1 is 2223393ad1d5ffdd62da79e1546de79c6259dc12. On Thu, Sep 28, 2017 at 10:52 AM, Andrew Wang <andrew.w...@cloudera.com> wrote: > Hi folks, > > We've driven the blocker count down t

Heads up: branching branch-3.0.0-beta1 off of branch-3.0

Hi folks, We've driven the blocker count down to 0, and I went through and made sure the fix versions and release notes and so on are all lined up. I'm going to cut branch-3.0.0-beta1 off branch-3.0 and try and get RC0 out today. Cheers, Andrew

[jira] [Reopened] (HADOOP-13917) Ensure yetus personality runs the integration tests for the shaded client

[ https://issues.apache.org/jira/browse/HADOOP-13917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-13917: -- > Ensure yetus personality runs the integration tests for the shaded cli

[jira] [Resolved] (HADOOP-13917) Ensure yetus personality runs the integration tests for the shaded client

[ https://issues.apache.org/jira/browse/HADOOP-13917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-13917. -- Resolution: Delivered > Ensure yetus personality runs the integration tests for the sha

[jira] [Resolved] (HADOOP-14545) Uninitialized S3A instance NPEs on toString()

[ https://issues.apache.org/jira/browse/HADOOP-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-14545. -- Resolution: Duplicate > Uninitialized S3A instance NPEs on toStr

[jira] [Reopened] (HADOOP-14545) Uninitialized S3A instance NPEs on toString()

[ https://issues.apache.org/jira/browse/HADOOP-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14545: -- > Uninitialized S3A instance NPEs on toStr

[jira] [Resolved] (HADOOP-14834) Remove original S3A output stream

[ https://issues.apache.org/jira/browse/HADOOP-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-14834. -- Resolution: Duplicate > Remove original S3A output str

[jira] [Reopened] (HADOOP-14834) Remove original S3A output stream

[ https://issues.apache.org/jira/browse/HADOOP-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14834: -- > Remove original S3A output stream > - > >

[jira] [Resolved] (HADOOP-14879) Build failure due to failing hadoop-client-check-invariants for hadoop-client-runtime.jar

[ https://issues.apache.org/jira/browse/HADOOP-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-14879. -- Resolution: Done > Build failure due to failing hadoop-client-check-invariants for >

[jira] [Reopened] (HADOOP-14879) Build failure due to failing hadoop-client-check-invariants for hadoop-client-runtime.jar

[ https://issues.apache.org/jira/browse/HADOOP-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14879: -- > Build failure due to failing hadoop-client-check-invariants for > hadoop-client-runti

[jira] [Resolved] (HADOOP-11656) Classpath isolation for downstream clients

[ https://issues.apache.org/jira/browse/HADOOP-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-11656. -- Resolution: Done Hadoop Flags: (was: Incompatible change) Fix Version/s: 3.0.0

[jira] [Reopened] (HADOOP-14655) Update httpcore version to 4.4.6

[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14655: -- Reverted this JIRA from trunk and branch-3.0 per Marton's instructions. > Update httpc

2017-09-22 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-09-22 We've had some late breaking blockers related to Docker support that are delaying the release. We're on a day-by-day slip at this point. Highlights: - I did a successful test create-release

Re: [DISCUSS] moving to Apache Yetus Audience Annotations

's too late to get in for 3.0, I can make a jira and put it > on the back burner for when trunk goes to 4.0? > > On Fri, Sep 22, 2017 at 12:49 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > >> Is this itself an incompatible change? I imagine the bytecode will be >

Re: [DISCUSS] moving to Apache Yetus Audience Annotations

Is this itself an incompatible change? I imagine the bytecode will be different. I think we're too late to do this for beta1 given that I want to cut an RC0 today. On Fri, Sep 22, 2017 at 7:03 AM, Sean Busbey wrote: > When Apache Yetus formed, it started with several key

[jira] [Resolved] (HADOOP-14655) Update httpcore version to 4.4.6

[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-14655. -- Resolution: Fixed While it's in the branch, let's leave the JIRA resolved for release notes

2017-09-19 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-09-19 Sorry for the late update. We're down to one blocker and one EC must do! Made great progress over the last week and a bit. We will likely cut RC0 this week. Highlights: - Down to just two blocker

Re: [DISCUSS] Can we make our precommit test robust to dependency changes while staying usable?

On Thu, Sep 14, 2017 at 1:59 PM, Sean Busbey wrote: > > > On 2017-09-14 15:36, Chris Douglas wrote: > > This has gotten bad enough that people are dismissing legitimate test > > failures among the noise. > > > > On Thu, Sep 14, 2017 at 1:20 PM, Allen

Re: [VOTE] Merge yarn-native-services branch into trunk

ks, > Jian > > > > On Sep 7, 2017, at 3:59 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > > > > Hi folks, > > > > This vote closes today. I see a -1 from Allen on inclusion in beta1. I > see > > there's active fixing going on, but given

2017-09-07 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-09-07 Slightly early update since I'll be out tomorrow. We're one week out, and focus is on blocker burndown. Highlights: - 3.1.0 release planning is underway, led by Wangda. Target release date is in

[jira] [Created] (HADOOP-14848) Switch from JDiff to japicmp

Andrew Wang created HADOOP-14848: Summary: Switch from JDiff to japicmp Key: HADOOP-14848 URL: https://issues.apache.org/jira/browse/HADOOP-14848 Project: Hadoop Common Issue Type

Re: [VOTE] Merge yarn-native-services branch into trunk

Hi folks, This vote closes today. I see a -1 from Allen on inclusion in beta1. I see there's active fixing going on, but given that we're one week out from RC0, I think we should drop this from beta1. Allen, Jian, others, is this reasonable? What release should we retarget this for? I don't have

Re: DISCUSS: Hadoop Compatability Guidelines

There's also the DataNode data directory layout. FS edit logs should also be included if we're including the fsimage. Historically we've bumped these in minor and major releases, though I'm not sure whether precedent supports the practice. It means you can't downgrade, and features that need

Re: Moving Java Forward Faster

I read Mark Reinhold's blog [1] and overall like this change to release cadence. It introduces 3-year LTS releases along with the 6-month feature release cadence. We'd probably stick with the LTS releases. The blog says they only plan to support each LTS for 3 years though. I'd like this to

[jira] [Resolved] (HADOOP-13998) Merge initial S3guard release into trunk

[ https://issues.apache.org/jira/browse/HADOOP-13998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-13998. -- Resolution: Done Re-resolving per above. > Merge initial S3guard release into tr

[jira] [Reopened] (HADOOP-13998) Merge initial S3guard release into trunk

[ https://issues.apache.org/jira/browse/HADOOP-13998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-13998: -- Re-opening to resolve as "Complete" or something, since this code change was

2017-09-01 Hadoop 3 release status update

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-09-01 We're two weeks out from beta1, focus is on blocker burndown. Highlights: - S3Guard merged! - TSv2 alpha2 merged! - branch-3.0 has been cut after discussion on dev lists. Red flags: - 10

Heads up: branch-3.0 has been cut, commit here for 3.0.0-beta1

Hi folks, I've proceeded with the plan from our earlier thread and cut branch-3.0. The branches and maven versions are now set as follows: trunk: 3.1.0-SNAPSHOT branch-3.0: 3.0.0-beta1-SNAPSHOT branch-2's are still the same. This means if you want to commit something for beta1, commit it to

Re: [DISCUSS] Branches and versions for Hadoop 3

ching. > > Regards, > Varun Saxena. > > On Tue, Aug 29, 2017 at 11:35 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > >> Sure. Ping me when the TSv2 goes in, and I can take care of branching. >> >> We're still waiting on the native services and S3

[jira] [Reopened] (HADOOP-14674) Correct javadoc for getRandomizedTempPath

[ https://issues.apache.org/jira/browse/HADOOP-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14674: -- I don't see this showing up in trunk, did it actually get committed? > Correct java

Re: Branch merges and 3.0.0-beta1 scope

Hi Vinod, On Fri, Aug 25, 2017 at 2:42 PM, Vinod Kumar Vavilapalli wrote: > > From a release management perspective, it's *extremely* reasonable to > block the inclusion of new features a month from the planned release date. > A typical software development lifecycle

Re: [DISCUSS] Branches and versions for Hadoop 3

hold commit until you cut the two branches >> and TSv2 get committed. >> >> Thanks, >> Wangda >> >> On Tue, Aug 29, 2017 at 11:25 AM, Andrew Wang <andrew.w...@cloudera.com> >> wrote: >> >> > Hi Wangda, >> > >> > I'll cut

Re: [DISCUSS] Branches and versions for Hadoop 3

TSv2, resource profile, YARN-5734) are > targeted to merge to 3.0-GA but not 3.0-beta1, which branch we should > commit to, and when we can commit? Also, similar to 3.0.0-alpha1 to 4, you > will cut branch-3.0.0-beta1, correct? > > Thanks, > Wangda > > > On Tue, Aug 29, 2017

Re: [DISCUSS] Branches and versions for Hadoop 3

> @Wangda: your resource profile vote ends tomorrow, could we please > coordinate our merges? > > thanks > Vrushali > > > On Mon, Aug 28, 2017 at 10:45 PM, Rohith Sharma K S < > rohithsharm...@apache.org> wrote: > >> On 29 August 2017 at 06:24, Andrew Wang

Re: [DISCUSS] Branches and versions for Hadoop 3

So far I've seen no -1's to the branching proposal, so I plan to execute this tomorrow unless there's further feedback. Regarding the above discussion, I think Jason and I have essentially the same opinion. I hope that keeping trunk a release branch means a higher bar for merges and code review

2017-08-25 Hadoop 3 release status update

Hi all, I've written up a status report for the current state of Hadoop 3 on the wiki. I've also pasted it below for your convenience. Cheers, Andrew https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates 2017-08-25 Another month flew by without an update. This is

Re: Branch merges and 3.0.0-beta1 scope

ll continue tests to make sure >> changes are safe. >> >> Discussed with Andrew offline, we decided to not put this to beta1 since >> beta1 is not far away. But we want to put it before GA if sufficient tests >> are done. >> >> Thanks, >> Wangda &g

Re: Branch merges and 3.0.0-beta1 scope

at 10:54 AM, Rohith Sharma K S < > rohithsharm...@apache.org> wrote: > >> On 25 August 2017 at 22:39, Andrew Wang <andrew.w...@cloudera.com> wrote: >> >> > Hi Rohith, >> > >> > Given that we're advertising TSv2 as an alpha feature,

[DISCUSS] Branches and versions for Hadoop 3

Hi folks, With 3.0.0-beta1 fast approaching, I wanted to go over the proposed branching strategy. In the early 2.x days, moving trunk immediately to 3.0.0 was a mistake. branch-2 and trunk were virtually identical, and increased backport complexity. Until we need to make incompatible changes,

Re: Branch merges and 3.0.0-beta1 scope

Hi Jason, I agree with this proposal. I'll start another email thread spelling this out, and gather additional feedback. Best, Andrew On Fri, Aug 25, 2017 at 6:27 AM, Jason Lowe <jl...@oath.com> wrote: > Andrew Wang wrote: > > >> This means I'll cut branch-3 and >>

Re: Branch merges and 3.0.0-beta1 scope

compatibility would be a > matter. > During this gap i.e between beta-GA release, should we maintain > compatibility ? > If my understanding is right then TSv2 have to be merged with beta1 > release. In TSv2 phase-2, we have compatibility changes from phase-1. > > > Thanks &

Re: Branch merges and 3.0.0-beta1 scope

Glad to see the discussion continued in my absence :) >From a release management perspective, it's *extremely* reasonable to block the inclusion of new features a month from the planned release date. A typical software development lifecycle includes weeks of feature freeze and weeks of code

  1   2   3   4   5   6   >