Ok, we are nearly there. # The new YARN jira is functional now (albeit with some teething issues with notifications/workflow which should be resolved soon): https://issues.apache.org/jira/browse/YARN # I've committed YARN-1 to move YARN out of hadoop-mapreduce-project onto hadoop-yarn-project in subversion. # The yarn-dev@ mailing list is active. # All jira notifications are going to yarn-issues@ and all subversion commit notifications are going to yarn-commits@.
Please do subscribe to the relevant mailing lists. Also note that there is *no* yarn-user@ since all user interactions are now via u...@hadoop.apache.org. If you see issues, please let me know and I'll try to respond ASAP. thanks, Arun On Aug 3, 2012, at 12:51 AM, Arun C Murthy wrote: > With 22 +1s (9 binding) and no -1s the vote passes unanimously. Thanks to all > who voted. > > I'll start the necessary process to move on this. > > thanks, > Arun > > On Jul 26, 2012, at 8:24 PM, Arun C Murthy wrote: > >> As we discussed in the previous thread, I'd like to call a vote to establish >> YARN as a sub-project (it's the best *term* we have to describe it in our >> current nomenclature) of Apache Hadoop along with Common, HDFS & MapReduce. >> >> Specifically, >> # Create a separate top-level src folder hadoop-yarn, move it out of >> hadoop-mapreduce-project in subversion at hadoop/common/trunk. >> # Create a separate YARN jira project and yarn-dev@ mailing-list. >> # Continue to co-release a single Hadoop release with Common, HDFS, YARN & >> MapReduce. >> >> Please vote, the vote will run the normal 7 days. Obviously, I'm +1. >> >> thanks, >> Arun >> > > -- > Arun C. Murthy > Hortonworks Inc. > http://hortonworks.com/ > > -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
