Wowza. RYA-7 resulted in 49 emails!? One email per diff. Is this
something configurable? I don't recall ever seeing that before on other
projects.
But, on topic... I'm a fan of Sean's recommendation for a mailing list
dedicated to general "non-human-generated" messages (commits, CI, etc).
Sean Busbey wrote:
When the Apache Yetus PMC was setting up resources we were going to
skip a dedicated commits list and a few folks spoke up about teh
utility of a dedicated commits alias. I personally don't mind having
things mixed up, but mailing lists are cheap so I generally recommend
taking on things that folks find useful.
If you're going to make an additional mailing list to handle
non-commit automated emails, I'd recommend making it something like
"notifications@rya" instead of "issues@rya" so that when e.g. y'all
add automated CI builds those same emails can go there.
On Thu, Dec 3, 2015 at 8:27 AM, Adina Crainiceanu<[email protected]> wrote:
I agree, commits should go to commits not dev. The mailing list is
configured such that replies go to dev list, which I think is appropriate.
I saw that some projects send the issue tracking changes to commits, rather
than creating a new mailing list for issues@. For now, should we just
configure the issue tracker to send the automated messages to commits, and
then create an issues message list later, or would people prefer an issues
list right now?
On Thu, Dec 3, 2015 at 8:16 AM, Puja Valiyil<[email protected]> wrote:
Commits go to commits. Aaron had also wanted to set up an issues list
where things related to jira and automated build related email traffic
would go.
Sent from my iPhone
On Dec 3, 2015, at 3:04 AM, Sean Busbey<[email protected]> wrote:
Heya folks,
We have a commits@rya list, but right now all the commit notifications
go to dev@rya.
Would folks prefer that we keep everything going to dev, or change
things so that commits go to commits?
-Sean
--
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/
