[
https://issues.apache.org/jira/browse/STDCXX-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526276
]
Martin Sebor commented on STDCXX-546:
-------------------------------------
A few Apache projects, including one in the Incubator, have set up an -issues
list exclusively for Jira email notifications (see below). It might make sense
for use to do the same to cut down on the amount of "spam" on the -dev list. It
would probably be best to hold off on this until graduation since at that point
INFRA will have to set up a whole bunch of lists for us anyway.
http://mail-archives.apache.org/mod_mbox/www-infrastructure-issues/
http://mail-archives.apache.org/mod_mbox/commons-issues/
http://mail-archives.apache.org/mod_mbox/incubator-adffaces-issues/
http://mail-archives.apache.org/mod_mbox/maven-issues/
http://mail-archives.apache.org/mod_mbox/shale-issues/
http://mail-archives.apache.org/mod_mbox/struts-issues/
http://mail-archives.apache.org/mod_mbox/tiles-issues/
> Create new mailing list specifically for JIRA change logs.
> ----------------------------------------------------------
>
> Key: STDCXX-546
> URL: https://issues.apache.org/jira/browse/STDCXX-546
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Web
> Reporter: Eric Lemings
> Priority: Minor
>
> Currently, change logs created by creating, editing, and updating JIRA issues
> are sent to the stdcxx-dev mailing list. Suggest creating a new stdcxx-jira
> mailing list specifically for these messages. (Not sure if Subversion change
> logs are automatically sent to a mailing list but, if they are, a separate
> stdcxx-svn mailing list should also be created for these messages.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
