Re: PRs and reviews

FYI, I asked the infrastructure-dev mailing list about merging github PRs, and these are the answers I got: http://mail-archives.apache.org/mod_mbox/www-infrastructure-dev/201510.mbox/%3CCANyrgveNjTDWOXj6fM4v2hRhJXwB%3DS2ko8rZ_2if6AY2c-Knyw%40mail.gmail.com%3E and

PRs and reviews

I'd like to discuss how we do PRs and code reviews. Right now we are using github most likely because that's how we did it before Apache. Now the code lives in the Apache hosted repo and we have Review Board available to us. My assumption is that we are individually more familiar with one way or

[jira] [Resolved] (MYRIAD-114) Automatic dashboard building

[ https://issues.apache.org/jira/browse/MYRIAD-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Marella resolved MYRIAD-114. Resolution: Fixed > Automatic dashboard building > > >

[jira] [Resolved] (MYRIAD-98) Move from 4 spaces to 2 spaces for indentation

[ https://issues.apache.org/jira/browse/MYRIAD-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Marella resolved MYRIAD-98. --- Resolution: Fixed Assignee: Jim Klucar Fixed with following PRs:

[jira] [Updated] (MYRIAD-32) Vagrant instructions incomplete/ambiguous

[ https://issues.apache.org/jira/browse/MYRIAD-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Marella updated MYRIAD-32: -- Fix Version/s: (was: Myriad 0.1.0) > Vagrant instructions incomplete/ambiguous >