+1 This is a bit aside, but are we also getting jenkins machine in the apache domain?
Tom On Friday, February 7, 2014 1:54 AM, Kostas Sakellis <kos...@cloudera.com> wrote: +1 On Thursday, February 6, 2014, Sandy Ryza <sandy.r...@cloudera.com> wrote: > +1 > > > On Thu, Feb 6, 2014 at 4:10 PM, Mridul Muralidharan > <mri...@gmail.com<javascript:;> > >wrote: > > > +1 > > > > Would be great if the JIRA tag was 'clickable' to go to the actual JIRA > :-) > > > > Regards, > > Mridul > > > > > > On Fri, Feb 7, 2014 at 5:35 AM, Patrick Wendell > > <pwend...@gmail.com<javascript:;> > > > > wrote: > > > As a break out from the other thread. I'd like to propose two > > > guidelines for pull requests. These guidelines are to make things > > > easier to track for developers and users, and to help organize the > > > large number of PR's that we are receiving. Thoughts? > > > > > > 1. Pull requests will require associated JIRA's. We will ask people to > > > create a JIRA if there is none yet. > > > > > > 2. Pull request names should ideally convey: > > > (a) The JIRA name > > > (b) A title summarizing the patch > > > (c) [optional prefix] The library it is related to > > > (d) [optional prefix] WIP or RFC if it is not finished. > > > > > > Example names: > > > SPARK-123: Add some feature to Spark > > > [STREAMING] SPARK-123: Add some feature to Spark streaming > > > [MLLIB] [WIP] SPARK-123: Some potentially useful feature for MLLib > > > > > > - Patrick > > >
