Re: Why there are so many revert operations on trunk?

inline On Mon, Jun 6, 2016 at 4:36 PM, Vinod Kumar Vavilapalli wrote: > Folks, > > It is truly disappointing how we are escalating situations that can be > resolved through basic communication. > > Things that shouldn’t have happened > - After a few objections were

Re: Why there are so many revert operations on trunk?

This seems like something that is going to probably happen again if we continue to cut releases from trunk. I know that this has been discussed at length in a separate thread but I think it would be good to recognize that it is the core of the issue here. Either we: * need to define what will

Re: Why there are so many revert operations on trunk?

To clarify what happened here, I moved the commits to a feature branch, not just reverting the commits. The intent was to make it easy to merge back in later, and also to unblock the 2.8 and 3.0 releases we've been trying very hard to wrap up for weeks. This doesn't slow down development since you

Re: Why there are so many revert operations on trunk?

Colin raised the -1 demanding a design document. The document was added the very next day. There were constructive discussions on the design. There was a demand for listenable future or futures with callback, which was accepted to accommodate. Rest of the work having been completed, there was

Re: Why there are so many revert operations on trunk?

Reading through HDFS-9924, a request for a design doc- and a -1 on committing to trunk- was raised in mid-May, but commits to trunk continued. Why is that? Shouldn't this have paused while the details were discussed? Branching is neutral to the pace of feature development, but consensus on the

Re: Why there are so many revert operations on trunk?

Thanks Aaron for pointing it out. I didn't see any consensus on HDFS-9924 so I think we should bring it here with broader audiences for more discussions. I saw several very bad practices here: 1. committer (no need to say who) revert all commits from trunk without making consensus with all

Re: Why there are so many revert operations on trunk?

Junping, All of this is being discussed on HDFS-9924. Suggest you follow the conversation there. -- Aaron T. Myers Software Engineer, Cloudera On Mon, Jun 6, 2016 at 7:20 AM, Junping Du wrote: > Hi Andrew, > > I just noticed you revert 8 commits on trunk last

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/49/ No changes -1 overall The following subsystems voted -1: findbugs unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint

Why there are so many revert operations on trunk?

Hi Andrew, I just noticed you revert 8 commits on trunk last Friday: HADOOP-13226 HDFS-10430 HDFS-10431 HDFS-10390 HADOOP-13168 HDFS-10390 HADOOP-13168 HDFS-10346 HADOOP-12957 HDFS-10224 And I didn't see you have any comments on JIRA or email discussion before you did this. I