Fwd: Mozilla IT wants to make cvs.mozilla.org read-only in Q2 2012
Brian Smith <[email protected]> Wed, 21 Mar 2012 12:37:33 -0700 (PDT)
| Newsgroups | gmane.comp.mozilla.devel.nspr |
|---|---|
| Message-ID | <255817262.15483371.1332358653452.JavaMail.root@zimbra1.shared.sjc1.mozilla.com> |
----- Forwarded Message ----- Subject: Mozilla IT wants to make cvs.mozilla.org read-only in Q2 2012 As I mentioned in a previous email, Mozilla Corp. does not want to maintain the CVS server any more. I was told today that our IT team would like to make cvs.mozilla.org read-only ASAP. I suggested that it isn't realistic to do so immediately, but that we should be able to find a solution by the end of Q2. My understanding is that IT is planning to keep cvs(-mirror).mozilla.org running in READ-ONLY mode indefinitely after Q2. I will help our IT/releng teams create a copy of the CVS server (with full history of NSPR and NSS since the original open-sourcing of each) in Mercurial, and to convert the NSPR and NSS testing infrastructure into one that works with Mozilla's normal test infrastructure. This would be the "NSPR/NSS project branch." My understanding is that there are already resources in releng/IT reserved to do this work. The idea is that we (Gecko/Firefox developers) would merge the CVS HEAD into this Mercurial repository, and then let it run the whole NSPR/NSS test suite. Once that test suite passes, we would merge the NSS project branch into mozilla-central/-aurora/-beta. Also, once this is done, every NSPR/NSS developer will be able to use our tryserver to test changes to NSPR and NSS before they are committed to the CVS HEAD. The main question is: who will host the CVS server? My proposal is that we make MoCo's Mercurial-based NSS project branch the new home of NSPR and NSS, and avoid CVS completely going forward. Mozilla is planning to create the NSPR/NSS project branch anyway. Mozilla is more than happy to facilitate other projects' needs in the NSS project branch, in the same way that we do for the current CVS server. (That is, regardless of whether or not their is a CVS server, we are not trying to fork NSPR or NSS.) I invite counter-proposals. The main requirement for counter-proposals is that Mozilla IT/releng must not be responsible for maintaining a CVS server (that isn't read-only) by the end of Q2. Cheers, Brian