A few assorted things

[Josh Elser <jo...@gmail.com>]

Hey folks,

* If you haven't seen already, Avatica is no longer in the calcite.git 
repo, but in a sister calcite-avatica.git repo.
* I've permanently allowed both Jenkins and Github emails to be sent to 
the dev list. If we want these elsewhere, we can consider that.
* I've consolidated the Jenkins jobs for Avatica in 
https://builds.apache.org/view/All/job/Calcite-Avatica-Master/. This 
single job will build across JDK7, 8, and 9.

- Josh

Re: A few assorted things

[James Taylor <ja...@apache.org>]

PRs are tied to JIRA cases based on the git commit message containing the
project name and JIRA number (i.e. CALCITE-####). This will cause PR
comment to generate JIRA comments. You may need to file an infra ticket to
get this setup.

On Sun, Apr 2, 2017 at 5:34 PM Julian Hyde <jh...@apache.org> wrote:

> Many thanks, Josh, for moving Avatica to its own repo. A much needed
> re-potting.
>
> As Avatica becomes more successful, I noticed a couple of sites referring
> to “Apache Avatica”. I’ve started a thread discussing how we want Avatica
> to be branded.
>
> A while back we changed notifications so that commits went to the commits
> list, and only the first message per JIRA case went to the dev list. I
> think this was a big improvement in the level of traffic on dev. I am very
> pleased that we keep the traffic below 200 most months[1].
>
> I fear that GitHub review comments will push the traffic unacceptably
> higher. (We fix about 100 issues in a 3 month release, and if each of those
> has 3 review comments, that’s 100 extra emails on the list per month.)
> Since pull requests are almost always associated with a JIRA case, I would
> rather that only people who have chosen to watch that JIRA case get
> notified. I don’t know whether it’s possible to tie PRs to JIRA cases.
>
> Julian
>
> [1] https://mail-archives.apache.org/mod_mbox/calcite-dev/ <
> https://mail-archives.apache.org/mod_mbox/calcite-dev/>
>
> > On Apr 2, 2017, at 2:47 PM, Jacques Nadeau <ja...@apache.org> wrote:
> >
> > That's great Josh. Thanks!
> >
> > On Sun, Apr 2, 2017 at 2:04 PM, Josh Elser <jo...@gmail.com> wrote:
> >
> >> Hey folks,
> >>
> >> * If you haven't seen already, Avatica is no longer in the calcite.git
> >> repo, but in a sister calcite-avatica.git repo.
> >> * I've permanently allowed both Jenkins and Github emails to be sent to
> >> the dev list. If we want these elsewhere, we can consider that.
> >> * I've consolidated the Jenkins jobs for Avatica in
> >> https://builds.apache.org/view/All/job/Calcite-Avatica-Master/. This
> >> single job will build across JDK7, 8, and 9.
> >>
> >> - Josh
> >>
>
>

Re: A few assorted things

[Josh Elser <jo...@gmail.com>]

Josh Elser wrote:
> Julian Hyde wrote:
>> I fear that GitHub review comments will push the traffic unacceptably
>> higher. (We fix about 100 issues in a 3 month release, and if each of
>> those has 3 review comments, that\u2019s 100 extra emails on the list per
>> month.) Since pull requests are almost always associated with a JIRA
>> case, I would rather that only people who have chosen to watch that
>> JIRA case get notified. I don\u2019t know whether it\u2019s possible to tie PRs
>> to JIRA cases.
>
> That's a very real fear :)
>
> I would assume that it's possible to remove Github emails to the dev
> list and instead rely on the JIRA comments automatically placed by the
> Github integration. I think the only downside here is that pull requests
> could be "lost" if the creator doesn't put a JIRA id in the pull-request
> subject line.
>
> I can file a JIRA issue asking if the dev-list emails piece are an
> "optional" component of the github integration. Otherwise, I can
> un-moderate the chatter (and just set up a filter to not bug me :D)

I hit the threshold myself :)

calcite-avatica.git Github email to dev@ should be going to /dev/null 
(per Pono @asfinfra). We'll now just get them once via the JIRA 
commenting. I don't _recall_ seeing the same for calcite.git, but if 
that is the case, it's an easy ask in the hipchat room.

Re: A few assorted things

[Josh Elser <jo...@gmail.com>]

Julian Hyde wrote:
> I fear that GitHub review comments will push the traffic unacceptably higher. (We fix about 100 issues in a 3 month release, and if each of those has 3 review comments, that\u2019s 100 extra emails on the list per month.) Since pull requests are almost always associated with a JIRA case, I would rather that only people who have chosen to watch that JIRA case get notified. I don\u2019t know whether it\u2019s possible to tie PRs to JIRA cases.

That's a very real fear :)

I would assume that it's possible to remove Github emails to the dev 
list and instead rely on the JIRA comments automatically placed by the 
Github integration. I think the only downside here is that pull requests 
could be "lost" if the creator doesn't put a JIRA id in the pull-request 
subject line.

I can file a JIRA issue asking if the dev-list emails piece are an 
"optional" component of the github integration. Otherwise, I can 
un-moderate the chatter (and just set up a filter to not bug me :D)

Re: A few assorted things

[Julian Hyde <jh...@apache.org>]

Many thanks, Josh, for moving Avatica to its own repo. A much needed re-potting.

As Avatica becomes more successful, I noticed a couple of sites referring to “Apache Avatica”. I’ve started a thread discussing how we want Avatica to be branded.

A while back we changed notifications so that commits went to the commits list, and only the first message per JIRA case went to the dev list. I think this was a big improvement in the level of traffic on dev. I am very pleased that we keep the traffic below 200 most months[1].

I fear that GitHub review comments will push the traffic unacceptably higher. (We fix about 100 issues in a 3 month release, and if each of those has 3 review comments, that’s 100 extra emails on the list per month.) Since pull requests are almost always associated with a JIRA case, I would rather that only people who have chosen to watch that JIRA case get notified. I don’t know whether it’s possible to tie PRs to JIRA cases.

Julian

[1] https://mail-archives.apache.org/mod_mbox/calcite-dev/ <https://mail-archives.apache.org/mod_mbox/calcite-dev/>

> On Apr 2, 2017, at 2:47 PM, Jacques Nadeau <ja...@apache.org> wrote:
> 
> That's great Josh. Thanks!
> 
> On Sun, Apr 2, 2017 at 2:04 PM, Josh Elser <jo...@gmail.com> wrote:
> 
>> Hey folks,
>> 
>> * If you haven't seen already, Avatica is no longer in the calcite.git
>> repo, but in a sister calcite-avatica.git repo.
>> * I've permanently allowed both Jenkins and Github emails to be sent to
>> the dev list. If we want these elsewhere, we can consider that.
>> * I've consolidated the Jenkins jobs for Avatica in
>> https://builds.apache.org/view/All/job/Calcite-Avatica-Master/. This
>> single job will build across JDK7, 8, and 9.
>> 
>> - Josh
>> 

Re: A few assorted things

[Jacques Nadeau <ja...@apache.org>]

That's great Josh. Thanks!

On Sun, Apr 2, 2017 at 2:04 PM, Josh Elser <jo...@gmail.com> wrote:

> Hey folks,
>
> * If you haven't seen already, Avatica is no longer in the calcite.git
> repo, but in a sister calcite-avatica.git repo.
> * I've permanently allowed both Jenkins and Github emails to be sent to
> the dev list. If we want these elsewhere, we can consider that.
> * I've consolidated the Jenkins jobs for Avatica in
> https://builds.apache.org/view/All/job/Calcite-Avatica-Master/. This
> single job will build across JDK7, 8, and 9.
>
> - Josh
>