Sylvestre is working on automating updates to these modules as part of the release process. We have a staging svn server, but it appears to be backed by the same data store as production. In order to test his changes now (and to make staging releases work going forward), we'd like a few things: 1) Staging copies of /libs/product-details and /projects/mozilla.com that we can use in testing. 2) Give stage-ffxbld and stage-tbirdbld commit access to these new modules via svn.allizom.org. 3) Give ffxbld and tbirdbld commit access to /lib/product-details and /projects/mozilla.com through svn.mozilla.org. Because we're testing automating that does things like commit to svn, we can't use git or hg for this.

(In reply to Ben Hearsum [:bhearsum] from comment #0) > Sylvestre is working on automating updates to these modules as part of the > release process. We have a staging svn server, but it appears to be backed > by the same data store as production. In order to test his changes now (and > to make staging releases work going forward), we'd like a few things: > 1) Staging copies of /libs/product-details and /projects/mozilla.com that we > can use in testing. > 2) Give stage-ffxbld and stage-tbirdbld commit access to these new modules > via svn.allizom.org. Scratch #1 and #2 - we decided it's not worth the effort to implement in staging. > 3) Give ffxbld and tbirdbld commit access to /lib/product-details and > /projects/mozilla.com through svn.mozilla.org. How can we get this part prioritized?

It looks like ffxbld and tbirdbld do not have SVN access enabled. If you file a bug with the MOC to have that enabled in LDAP, I can add them to the SVN authz file and grant access.

Added in r100702, and prodded puppet, so you should be good to go. Shout if you run into issues.

(In reply to Kendall Libby [:fubar] from comment #3) > Added in r100702, and prodded puppet, so you should be good to go. Shout if > you run into issues. I just verified the access - thanks!