On by default: +1 Separate JIRA account: makes sense Concerns about -1/+1 in CTR: it's informs the committers, but isn't binding, so I'm not concerned
Questions: Is this just for PRs or patches, too? If patches also, how do we identify patches vs. other JIRA attachments? How do other committers/PMC tweak/modify the settings? Are permissions similar to Jenkins at builds.apache.org? On Fri, Jan 8, 2016 at 1:41 PM John Vines <[email protected]> wrote: > +1 > > On Fri, Jan 8, 2016 at 12:58 PM Keith Turner <[email protected]> wrote: > > > +1 > > > > On Fri, Jan 8, 2016 at 12:24 PM, Josh Elser <[email protected]> > wrote: > > > > > Hi, > > > > > > Per the other thread "Yetus Accumulo 'Personality'" [1], I'd like to > see > > > what people think about turning this on by default. > > > > > > I've been talking to Sean in chat today who had made a suggestion that > we > > > get our own JIRA acct instead of the "Hadoop QA" user. Aside from that, > > I'm > > > pretty happy with this. > > > > > > There is likely further tweaking we can do (e.g. multijdk builds, try > the > > > sunny-day ITs). One big concern is the presence of a -1/+1 in an CTR > > > community. We would need some docs to be clear that the PreCommit > comment > > > is a tool for vetting contributions, not a bar that must be satisfied > > prior > > > to commit (this is a simple website update). > > > > > > Anywho -- if you have opinions, please let them be heard now. If there > > > isn't any argument against, I'll move ahead with this in time. > > > > > > > > > [1] > > > > > > http://mail-archives.apache.org/mod_mbox/accumulo-dev/201601.mbox/%[email protected]%3E > > > > > >
