RE: How to best manage authorization after tag/branch creation?

> If you need to control access to the code you can do things such as:
> - only allow the developers that need access access to the whole project

Yep, we do this. There are still some restricted areas in some projects
though.

> - setup a secondary tags namespace for special binary only information
> - have the build mechanism push the binaries to a special binary tag by the
> same
> name
> - use svn:externals to reference the binary releases instead of source
> releases.

Yes, I think binary releases of restricted modules is a very good idea. It's
a slow process, but I think pushing for this will help a lot. There's a
perception that binary releases of restricted source code is not necessary
if product-specific changes are needed to the code. Just copy the source
code to the product folder and restrict it in httpd.conf. I'm working on
this... Also, while we don't use svn:externals currently, it looks like
it would be useful for handling binary releases of restricted code. Thanks
for that!
Received on 2010-10-13 22:56:30 CEST