Re: Logistics for releasing 2.4

On Wed, Jan 22, 2014 at 5:21 PM, Arun C Murthy wrote: > Andrew, > > > On Jan 22, 2014, at 12:04 PM, Andrew Wang > wrote: > > > Monthly releases make no sense to me. > > I think the 'monthly' was a rough measure. Every 6-8 weeks works too. A regular release schedule works nicely over in hbasela

Re: Logistics for releasing 2.4

There are a couple of minor doc changes if they can be included in the next release that will be great. https://issues.apache.org/jira/browse/HADOOP-10050 https://issues.apache.org/jira/browse/HADOOP-10065 Thanks -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jan 22, 2014, at 6:09

Re: Logistics for releasing 2.4

Sounds good, thanks. I'll ping you off-thread. Arun On Wed, Jan 22, 2014 at 6:01 PM, Andrew Wang wrote: > Hi Arun, thanks for the reply. I hope that I've come across as an earnest > and motivated contributor who wants to help make high-quality releases. > Volunteering myself as RM and pushing f

Re: Logistics for releasing 2.4

Hi Arun, thanks for the reply. I hope that I've come across as an earnest and motivated contributor who wants to help make high-quality releases. Volunteering myself as RM and pushing for a 2.4 was not a reflection on your stewardship of 2.x so far. I know it's a lot of work. I didn't mean to sugg

Re: Logistics for releasing 2.4

Thanks Vinod. I'll start the work to re-spin 2.3 by changing jira numbers, CHANGES.txt etc. now. Arun On Wed, Jan 22, 2014 at 5:59 PM, Vinod Kumar Vavilapalli wrote: > > On Jan 22, 2014, at 5:36 PM, Arun C Murthy wrote: > > Agree 2.3 is now very stale. > > So, as I understand, your motivatio

Re: Logistics for releasing 2.4

On Jan 22, 2014, at 5:36 PM, Arun C Murthy wrote: > Agree 2.3 is now very stale. > > So, as I understand, your motivation is to get HDFS-2832 & HDFS-4949 out, > correct? > > If so, that could be a better option - I can abandon the 2.3rc, and then > release current branch-2 as 2.3. Would that

Re: Logistics for releasing 2.4

> As to a more frequent release cadence, it seems like so far there's a lot > of support. I think downstreams would actually appreciate more frequent > releases. HBase at least only builds against release artifacts, so they end > up scrambling whenever we drop a new release. Releasing more often w

Re: Logistics for releasing 2.4

On Jan 22, 2014, at 5:14 PM, Andrew Wang wrote: > Another option (not to step on anyone's toes) is to scratch the current 2.3 > branch and make HDFS-2832+HDFS-4949 the new 2.3, since the current 2.3 has > sort of lost its way as a bugfix-only release, and has diverged quite a bit > from branch-2

Re: Logistics for releasing 2.4

Andrew, > On Jan 22, 2014, at 12:04 PM, Andrew Wang wrote: Monthly releases make no sense to me. They would result in a number of meaningless releases (of the 12 releases per year) of which most would be unstable and would lack features most folks want (for e.g. Yahoo has been clear that Rol

Re: Logistics for releasing 2.4

Hi Vinod, If the main point of contention is the alpha/beta/stable labeling for features, we can just not include anything but stable features in the proposed 2.4. This means HDFS-2832 and HDFS-4949 (along with the plethora of other improvements that have gone in since 2.2). AFAIK the previous pla

[jira] [Created] (HADOOP-10255) Copy the HttpServer in 2.2 back to branch-2

Haohui Mai created HADOOP-10255: --- Summary: Copy the HttpServer in 2.2 back to branch-2 Key: HADOOP-10255 URL: https://issues.apache.org/jira/browse/HADOOP-10255 Project: Hadoop Common Issue Typ

[jira] [Resolved] (HADOOP-10254) HttpServer doesn't load listeners

[ https://issues.apache.org/jira/browse/HADOOP-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang resolved HADOOP-10254. -- Resolution: Won't Fix Per HADOOP-10253, it will be cleaner to bring the original HttpServer b

Re: Logistics for releasing 2.4

I think YARN-149 will be ready if we do a 2.4 release sometime next month. The same goes for YARN-321 also. The merge-to-trunk vote is happening now and it should be in a good shape soon if we stick to the early plan that is laid out in the roadmap. Overall, a bunch of us in the YARN side have

Re: Logistics for releasing 2.4

+1 to releasing often. Also, like Vinod's idea of labeling individual features alpha/beta/stable. I am +1 to releasing 2.4 end of this month and including YARN-149 as "beta". I think the associated configs are stable; we might add new ones to make it simpler. We have been testing it internally in

Re: Logistics for releasing 2.4

Thanks for the comments everyone. Vinod, if you think YARN-149 isn't ready yet, we can leave it out. Alternatively, we could release note it as "beta" with said known issues, and let people kick the tires. It looks like a bunch of the core functionality is already in place. Unless anyone else obj

[jira] [Created] (HADOOP-10254) HttpServer doesn't load listeners

Jimmy Xiang created HADOOP-10254: Summary: HttpServer doesn't load listeners Key: HADOOP-10254 URL: https://issues.apache.org/jira/browse/HADOOP-10254 Project: Hadoop Common Issue Type: Bug

Re: Logistics for releasing 2.4

Thanks Andrew for bringing this up. +1 on more frequent releases and an effort at (roughly time-based release. We are working to get 'HDFS-5776 Support 'hedged' reads in DFSClient' to land in time for 2.4 (but don't hold up the release for us!) St.Ack On Tue, Jan 21, 2014 at 3:51 PM, Vinod Kum

[jira] [Created] (HADOOP-10253) Remove deprecated methods in HttpServer

Haohui Mai created HADOOP-10253: --- Summary: Remove deprecated methods in HttpServer Key: HADOOP-10253 URL: https://issues.apache.org/jira/browse/HADOOP-10253 Project: Hadoop Common Issue Type: B

[jira] [Created] (HADOOP-10252) HttpServer can't start if hostname is not specified

Jimmy Xiang created HADOOP-10252: Summary: HttpServer can't start if hostname is not specified Key: HADOOP-10252 URL: https://issues.apache.org/jira/browse/HADOOP-10252 Project: Hadoop Common

[jira] [Created] (HADOOP-10251) Both NameNodes could be in STANDBY State if SNN network is unstable

Vinay created HADOOP-10251: -- Summary: Both NameNodes could be in STANDBY State if SNN network is unstable Key: HADOOP-10251 URL: https://issues.apache.org/jira/browse/HADOOP-10251 Project: Hadoop Common

Re: Maintaining documentations

>> Akira, could you please resend a list of your patches that need reviewing >> if you have it handy. Here is the list of all the documentation patches I have. https://issues.apache.org/jira/browse/HADOOP-6350?jql=project%20in%20(HADOOP%2C%20YARN%2C%20HDFS%2C%20MAPREDUCE)%20AND%20resolution%20

Build failed in Jenkins: Hadoop-Common-trunk #1020

See Changes: [wang] Move HADOOP-10143 to 2.4 section of CHANGES.txt [arp] HDFS-5434. Change block placement policy constructors from package private to protected. (Buddy Taylor via Arpit Agarwal) [brandonli] HDFS-5748. Too much i