Re: [Bodington-developers] Bodington and WebLearn code

[Alexis O'C. <ale...@ou...>]

Jon Maber wrote:
>> 1) Stick with CVS and create a branch.
>> 2) Import the existing CVS to SVN and then branch in that.
>>
>> I think the latter idea is probably a good one. We were chuffed with the 
>> result of converting WebLearn from CVS to SVN - it captured all the 
>> history beautifully, so we have experience of doing that (with cvs2svn) 
>> and could definitely provide you with tips there.
>>
>>   
>>     
> If we create a branch in the (svn) source forge repository, how do we 
> import the oxford work into that branch while _preserving all the oxford 
> check ins and check in notes_.  I'm thinking of putting the branch off 
> of the trunk at the date when the oxford rep. started to drift off. 
> Obviously it would be easy to put the Oxford head on the branch but then 
> everyone would have to go to your svn to trace back edits etc. 
>   

I had answered your other points before attempting to answer what is in 
fact your meatiest question. On reflection, I'm going to have to give 
this one some more thought :-\ .

> Question 2 - can anyone recommend a good book on SVN?
>   

Yup, the official one published by O'Reilly - it's very well written. 
It's available online at:
http://svnbook.red-bean.com/

> Question 3 - there are oodles of graphical interfaces to cvs - any 
> decent ones for svn now?
>
> Ta,

TortoiseSVN is a nice simple one for Windows. There are 2 good ones for 
Eclipse  - Subversive 
(http://www.polarion.org/index.php?page=overview&project=subversive) and 
Subclipse (http://subclipse.tigris.org/). I personally use the latter. 
If you're still a NetBeans man there is a svn module for that, but it is 
a bit cr@p compared to the Eclipse ones ;-).


Alexis