[jira] [Commented] (INFRA-3653) merge Maven subproject lists into main commits, dev, users lists

["Brett Porter (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039532#comment-13039532 ] 

Brett Porter commented on INFRA-3653:
-------------------------------------

I let those users lists know they'd be shutdown. So they can closed, with the others merged into their corresponding lists.

> merge Maven subproject lists into main commits, dev, users lists
> ----------------------------------------------------------------
>
>                 Key: INFRA-3653
>                 URL: https://issues.apache.org/jira/browse/INFRA-3653
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Mark Struberg
>            Assignee: Tony Stevenson
>
> Since traffic on a few maven subprojects is pretty low, we decided to consolidate our mailing lists a bit.
> Currently committing to https://svn.apache.org/repos/asf/maven/wagon will send mails to wagon-commits.
> There is almost zero traffic those days
> http://markmail.org/search/?q=list%3Aorg.apache.maven.wagon-commits
> thus moving this info over to maven-commits is what we'd like to have.
> The basic tendency is to aggregate those mailing litsts even more. Should I ping the maven PMC and get a list which other projects should get folded too, or better create single Jiras for each separate list?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira