The ASF infra support all Hadoop and it's community projects CI requests, as well as other ASF projects.
>From my experience with other ASF projects the Jenkins support has been great. And also ASF infra is accepting help if you guys think you could spare time and knowledge. Henry On Tuesday, February 11, 2014, Mark Hamstra <m...@clearstorydata.com<javascript:_e(%7B%7D,'cvml','m...@clearstorydata.com');>> wrote: > Whether that is a good idea or not depends largely, I think, on who will > have control of that putative Apache Jenkins. The > AMPLab-now-mostly-Databricks guys (i.e. Andy and others) who did the work > of setting up, configuring and maintaining the current Jenkins have done a > great job and have been very responsive when Jenkins has needed attention. > I would require convincing that the Apache infra team could match that > performance. > > > On Tue, Feb 11, 2014 at 8:40 AM, Tom Graves <tgraves...@yahoo.com> wrote: > > > +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 > > > > > > > > > >
