On 23.04.2016, at 19:35, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Esteban, Hi Fabio,
On Apr 23, 2016, at 10:11 AM, Esteban Lorenzano estebanlm@gmail.com wrote:
Hi,
I would like to have a list of constraints so we can sort it (otherwise this will never happen… :S) So far I have:
- sqSCCSVersion.h adapt to git. In Pharo we already have something but I do not think is enough… I will take a look to this.
- do not break Cadence builds. AFAIK, nothing forbids jenkins to stop using SVN and start using GIT (we also use Jenkins for our builds and we didn’t found any problem)… someone has to do the change, but it should be fairly straightforward. Who is the person who can take this task? (I’d do it, but I suppose Cadence has access policy to that)
My colleague Bob Westergaard and I will have to do this. There is no way Cadence will allow people from outside to do so ;-)
So I like Fabio's suggestion of deprecating subversion. We can keep the subversion bridge for some time (6 months, 1 year?), announce when it is going away (if ever?) and give people time to transition.
Are y'all aware that Github automatically provides an SVN bridge?