You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2011/05/24 21:24:47 UTC
[jira] [Created] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
send Maven WAGON commit messages to maven-commits instead wagon-commits
-----------------------------------------------------------------------
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
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
[jira] [Closed] (INFRA-3653) merge Maven subproject lists into main
commits, dev, users lists
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson closed INFRA-3653.
---------------------------------
Resolution: Fixed
Enjoy!
> 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
[jira] [Commented] (INFRA-3653) merge Maven subproject lists into
main commits, dev, users lists
Posted by "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
[jira] [Commented] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038991#comment-13038991 ]
Tony Stevenson commented on INFRA-3653:
---------------------------------------
Well, once we get a definitive list I can get it done. The change will only take a few mins to edit the mailer config.
Not sure if we actually want to fold the old lists into the others. But we'll see.
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
[jira] [Commented] (INFRA-3653) merge Maven subproject lists into
main commits, dev, users lists
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051470#comment-13051470 ]
#asfinfra IRC Bot commented on INFRA-3653:
------------------------------------------
<gmcdonald> pctony did this around r790282
> 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
[jira] [Closed] (INFRA-3653) merge Maven subproject lists into main
commits, dev, users lists
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "Arnaud HERITIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038879#comment-13038879 ]
Arnaud HERITIER commented on INFRA-3653:
----------------------------------------
Acked. We want to merge back everything. thx for your help guys
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
>
> 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
[jira] [Commented] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038876#comment-13038876 ]
Mark Struberg commented on INFRA-3653:
--------------------------------------
txs gav!
Daniel Kulp gathered the following info:
We currently have:
[/maven]
for_paths = maven/
to_addr = commits@maven.apache.org
suppress_if_match = yes
bcc_addr = git@git.apache.org
[/maven/scm]
for_paths = maven/scm/
to_addr = scm-commits@maven.apache.org
bcc_addr = git@git.apache.org
[/maven/wagon]
for_paths = maven/wagon/
to_addr = wagon-commits@maven.apache.org
bcc_addr = git@git.apache.org
[/maven/doxia]
for_paths = maven/doxia/
to_addr = doxia-commits@maven.apache.org
bcc_addr = git@git.apache.org
[/maven/surefire]
for_paths = maven/surefire/
to_addr = surefire-commits@maven.apache.org
bcc_addr = git@git.apache.org
This all should be collapsed to just:
[/maven]
for_paths = maven/
to_addr = commits@maven.apache.org
suppress_if_match = yes
bcc_addr = git@git.apache.org
Please give us till tomorrow to review this list, I'll send a Maven PMC member over to here to ack it, oki?
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
>
> 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
[jira] [Updated] (INFRA-3653) merge Maven subproject lists into
main commits, dev, users lists
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated INFRA-3653:
--------------------------------
Summary: merge Maven subproject lists into main commits, dev, users lists (was: send Maven WAGON commit messages to maven-commits instead wagon-commits)
> 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
[jira] [Reopened] (INFRA-3653) merge Maven subproject lists into
main commits, dev, users lists
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reopened INFRA-3653:
---------------------------------
Thanks!
I can see that the subs lists got moved and the qmail files changed. However, the ezmlm directories under ~/lists/maven.apache.org are still there. This means that someone can resubscribe to the list normally, though never receive anything from it, which has some potential for confusion.
I think you still need to run the remove-list script (and then re-establish the .qmail redirect) that's in the apmail README under "Merging"
> 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
[jira] [Commented] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038988#comment-13038988 ]
Brett Porter commented on INFRA-3653:
-------------------------------------
the dev list also talked about folding in *-users@ and *-dev@ into their corresponding lists
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
[jira] [Commented] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039013#comment-13039013 ]
Brett Porter commented on INFRA-3653:
-------------------------------------
I was expecting the old archives retained as is, but the configuration removed, and the qmail file pointed to the other lists. As Gav said on #asfinfra - the instructions for merging lists should be fine here.
The lists are: users, dev, commits for each of wagon, surefire, doxia, scm
The discussion only started < 24h ago though, so let's give the dev@ list a bit of time to object.
Also should decide what to do with users... going from *-users to users@maven.apache.org is a traffic jump. I'm inclined to either just remove those lists, or merge with dev (as they are rather developer oriented).
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
[jira] [Assigned] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson reassigned INFRA-3653:
-------------------------------------
Assignee: Tony Stevenson
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
[jira] [Commented] (INFRA-3653) send Maven WAGON commit messages to
maven-commits instead wagon-commits
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038812#comment-13038812 ]
#asfinfra IRC Bot commented on INFRA-3653:
------------------------------------------
<gmcdonald> gather all the changes you need to this issue so they cna be done in one hit, thanks.
> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
> 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
>
> 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
[jira] [Commented] (INFRA-3653) merge Maven subproject lists into
main commits, dev, users lists
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041065#comment-13041065 ]
Tony Stevenson commented on INFRA-3653:
---------------------------------------
Ok - so I have updated asf-mailer.conf to flatten the svn commit messages into the single list.
I have also moved the subscribers from the dev, and commit lists into the top-level maven lists. I have also removed the subscribers from the users 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