www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-3653) merge Maven subproject lists into main commits, dev, users lists
Date Sat, 18 Jun 2011 07:57:48 GMT

     [ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

#asfinfra IRC Bot closed INFRA-3653.

    Resolution: Fixed

> 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


View raw message