Hi all,
if you read comments in INFRA-8435, you will notice that it seems that
INFRA cannot easily make, for our SVN repository, the paths /trunk /tags
/branches read-only while keeping the rest read-write - which was my
initial request.
Given that, and considering that we are currently managing our website
via svnpubsub at /site, I've received the proposal to remove /trunk
/tags /branches from our SVN repository - now that we have our new GIT
repository fully operational.
The only issue I can see with this is for our wiki pages which often
reference SVN paths, with special reference to /tags in release notes
and upgrade procedures.
Before taking any action, I thought it was worth to briefly have a
discussion about this: I'm proposing to remove /branches and /trunk and
to leave /tags as is (for the reason expressed above).
WDYT?
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
