> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mardi 9 août 2005 02:16 > To: Maven Developers List > Subject: [vote] rearrange commits lists > > Hi, > > Alan proposed we use the standard that is used when setting up Apache > projects these days (we're still on our 2003 setup). > > Here it is in summary, elaborated into a bit more detail: > > 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, > continuum-commits
+0. Not sure I would call it commits. I would create a list that would receive: - JIRA issues - SCM commits - Build successes/failures - repo notifications Not sure how to name it though. Could be [EMAIL PROTECTED] I'm fine with [EMAIL PROTECTED] too. > 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], > post to the list to let people know what they are in for and > instructions to unsubscribe What is [EMAIL PROTECTED] for? Do you mean [EMAIL PROTECTED] > 3) stop *-dev forwarding from commits lists ok > 4) reconfigure svn to put Maven commits to that list. I think Maven > plugin developers should keep across what's happening in the core, so > they can stay together, but the other subprojects remain separate. +1 > 5) keep JIRA and repository reports on [EMAIL PROTECTED] Hmm... Not sure about this one. My first reaction was to put them on the commits list but thinking about it, I'm not sure anymore. > 6) send continuum/ci messages to the relevant commits list +1 > 7) disband the old cvs lists +1 Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
