apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chinmay Kolhatkar <chin...@datatorrent.com>
Subject Re: auto-generated emails
Date Tue, 19 Jul 2016 04:15:02 GMT
Pramod,

My Suggestion is on the same lines as what Yogi suggested, except instead
of creating a seperate mailing list, send further mails to folks in the
comments.

-Chinmay.


On Tue, Jul 19, 2016 at 3:07 AM, Pramod Immaneni <pramod@datatorrent.com>
wrote:

> Chinmay are you suggesting the first mail only sent to folks mentioned and
> not everyone in the list? I like Yogi's suggestion on having a separate
> commits list where all commit emails go but initial emails are still sent
> to dev and dev can mostly focus on discussions.
>
> Anyone, wants to volunteer to investigate these options?
>
> Thanks
>
> On Fri, Jul 15, 2016 at 2:34 AM, Yogi Devendra <
> devendra.vyavahare@gmail.com
> > wrote:
>
> > +1 on reducing automated emails for comments on dev list.
> >
> > How about having separate mailing list such as commits@apex which would
> > have full archive of comments?
> >
> > New JIRA, PR can be sent to both dev, commits.
> >
> > ~ Yogi
> >
> > On 13 July 2016 at 10:22, Chinmay Kolhatkar <chinmay@datatorrent.com>
> > wrote:
> >
> > > Strongly +1 for this.
> > >
> > > For 1, can the mail be sent to someone who is mentioned in the PR? So
> for
> > > e.g., if I mention @PramodSSImmaneni , then Pramod will be part of PR
> > email
> > > notification all further back and forth communication for that PR.
> > >
> > > @Pramod, just using your name as an example.. :)
> > >
> > > - Chinmay.
> > >
> > >
> > > On Wed, Jul 13, 2016 at 3:18 AM, Munagala Ramanath <
> ram@datatorrent.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Ram
> > > >
> > > > On Tue, Jul 12, 2016 at 2:35 PM, Pramod Immaneni <
> > pramod@datatorrent.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I was wondering how everyone felt about the volume of
> auto-generated
> > > > emails
> > > > > on this list. Looks like multiple emails are generated and sent to
> > > > everyone
> > > > > on the list even for relatively smaller actions such as commenting
> > on a
> > > > > pull request, one from git, another from JIRA etc.
> > > > >
> > > > > Understanding that there is a need for openness, how about finding
> a
> > > > > balance. Here are some ideas. I do not know if all of these are
> > > > technically
> > > > > feasible.
> > > > >
> > > > > 1. An email is sent to all in the list when a new pull request is
> > > created
> > > > > or merged but email notifications for back and forth comments
> during
> > > the
> > > > > review are only sent to participants in that particular pull
> request.
> > > > > 2. Similar process as above with JIRA. If someone is interested in
> > all
> > > > the
> > > > > updates to JIRA, including those that come from the pull request,
> > they
> > > > can
> > > > > add themselves to the watch list for that particular JIRA.
> > > > >
> > > > > Thanks
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message