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/
