Yup, I'll do it. Colm.
On Fri, Oct 24, 2014 at 9:34 AM, Francesco Chicchiriccò <[email protected] > wrote: > Hi all, > it seems that this discussion has not got particular feedback - but not > even raised any concern; I am then about to act as proposed, e.g. remove > from SVN /branches and /trunk and to leave /tags (and the rest) as is. > I'll let you know when done. > > There will be likely the need to review our wiki in order to find > references to /trunk or /branches and to change into links to > https://git-wip-us.apache.org/repos/asf?p=syncope.git > Any volunteer? > > Regards. > > On 22/10/2014 15:47, Colm O hEigeartaigh wrote: > >> Seems reasonable to me. >> >> Colm. >> >> On Wed, Oct 22, 2014 at 8:10 AM, Francesco Chicchiriccò < >> [email protected]> wrote: >> >>> 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/ > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
