The committer lists needs to be everyone currently doing work on jbossas which is pretty large. Take whoever has made a commit in the past 6 months as a start.
-----Original Message----- From: Damon Sicore Sent: Saturday, February 11, 2006 1:14 PM To: jboss-development@lists.sourceforge.net Cc: Adrian Brock; QA; Tom Benninger; Eric Brown Subject: Re: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff OK... Seriously... It will take me about 15 mins to do the import, but more importantly, I'll need to get the list of committers added to the proper branch structures in svn. This will take me a bit of time to do first, but, I'll start now. After they are added, you can easily coordinate people using the new repo at your leisure. Do you have a list of committers, and only those committers, you want for these branches? Is there a subset of all the committers? Since we have directory level access controls, we can do this, and I recommend it. Also, I'd recommend making the switch.. officially... after Eric and TomBen get the anonsvn off the fisheye, committer, cvs, and [insert- every-other-app-here] machine. It's currently running at a load of 10 on a single proc machine (or something close). Eric? On Feb 11, 2006, at 2:38 PM, Scott M Stark wrote: ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
