Re: [RFC] source repository at Apache

I do not think I have a vote, but I have an opinion:-)

> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

I think that it is a bad idea.

(1) This means breaking all current revision numbers.

All comments in the logs and some files (say CHANGES) will point to
nowhere, or have to be changed, and there are some ugly syntaxes (eg
r6382-6). All outside references to revision numbers would also be dead.

Maybe it would make sense to have the apache svn modules in that
repository, but it does not make much sense for the whole project.

The initial revision number can be kept as a revision property, but that
does not help much, one would have to search to find it.

(2) I use this ASF repository as an example of what should not be done
with svn when I teach svn:-) I advocate that pretty independent projects
should be in independant repositories, and connections can be implemented
with svn:externals quite simply.

(3) very big repositories add a large burden to system administration,
e.g. if you want to dump/reload or the like it would take ages of
disruption. Moreover, the ASF repository uses subversion, subversion uses
subversion. From a system admin perspective, I'm not sure that I would
like to change the tool for the big repository as often I could test it
on a smaller one. I would have a different policy to maintain them.
If some new feature requires a dump/load some day, the main asf repository
will have to schedule some down time to enable it, while it could be
very quickly handled on a smaller repos.

> 2) svn.apache.org/repos/$VAR -- our own repository, potentially
> running a custom server

I would prefer that. No disruption, just a switch/relocate.

-- 
Fabien.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416456