Issue list?

[Owen O'Malley <ow...@gmail.com>]

All,
   As we move over to Apache infrastructure, we need to decide what works for the community. The dev list is getting a lot of traffic and is probably intimidating to new comers. Currently the notices are:

Pull Requests and issue creation/comment/close -> dev@
Git commit -> commits@

One pattern that works for Hive is to do:

PR and issue creation -> dev@
PR and issue comments/close -> issues@
Git commit -> commits@

I don’t know what options Apache Infra gives us for notifications, but we could ask. What do people think?

.. Owen

Re: Issue list?

[Ryan Blue <rb...@netflix.com.INVALID>]

I think it makes sense to sent issue comments to issues@. That will make it
easy to remove them or set up filters to handle them.

We can't really use the Arrow or Parquet solution because we're using
GitHub issues instead of JIRA.

On Tue, Nov 27, 2018 at 10:24 AM Uwe L. Korn <uw...@xhochy.com> wrote:

> We have nearly the same setup as Hive for Arrow and Parquet and this
> working really well. The main difference is that we don't have the git
> mails directly on the issues list but get them through JIRA where PR
> comments are posted as work logs. The work log workaround is only there
> because we don't want them to interfere with actual discussions on the
> issue.
>
> > Am 27.11.2018 um 18:36 schrieb Owen O'Malley <ow...@gmail.com>:
> >
> > All,
> >   As we move over to Apache infrastructure, we need to decide what works
> for the community. The dev list is getting a lot of traffic and is probably
> intimidating to new comers. Currently the notices are:
> >
> > Pull Requests and issue creation/comment/close -> dev@
> > Git commit -> commits@
> >
> > One pattern that works for Hive is to do:
> >
> > PR and issue creation -> dev@
> > PR and issue comments/close -> issues@
> > Git commit -> commits@
> >
> > I don’t know what options Apache Infra gives us for notifications, but
> we could ask. What do people think?
> >
> > .. Owen
> >
>
>

-- 
Ryan Blue
Software Engineer
Netflix

Re: Issue list?

["Uwe L. Korn" <uw...@xhochy.com>]

We have nearly the same setup as Hive for Arrow and Parquet and this working really well. The main difference is that we don't have the git mails directly on the issues list but get them through JIRA where PR comments are posted as work logs. The work log workaround is only there because we don't want them to interfere with actual discussions on the issue.

> Am 27.11.2018 um 18:36 schrieb Owen O'Malley <ow...@gmail.com>:
> 
> All,
>   As we move over to Apache infrastructure, we need to decide what works for the community. The dev list is getting a lot of traffic and is probably intimidating to new comers. Currently the notices are:
> 
> Pull Requests and issue creation/comment/close -> dev@
> Git commit -> commits@
> 
> One pattern that works for Hive is to do:
> 
> PR and issue creation -> dev@
> PR and issue comments/close -> issues@
> Git commit -> commits@
> 
> I don’t know what options Apache Infra gives us for notifications, but we could ask. What do people think?
> 
> .. Owen
>