1. Transition to SVN server: follow up P.Hristov 24/01/2008

2. Proposal: 18/10/2007 Convert the AliRoot CVS repository to Subversion –Organization AliRoot  –trunk –branches –tags AliEn - keep CVS fluka_vmc  –Features: copyright notice automatically inserted end-of-line style: native (to deal with Ctrl^M on Windows)  Keywords substitution: $Id$ No logs  Offline Bible and tutorial slides included Strict lock for documentation and binary files Pointer to the Root version (using the “externals” feature) Compilation, coding conventions, run tests as hooks

3. What is done? Conversion of the repository Installation and configuration of Apache2 server on alisoft.cern.ch Installation and configuration of subversion on the server Installation and configuration of ViewVC tool Administrative groups and SVN permissions E-mail messages and distribution lists FAQ page Updated Offline pages and links: installation, code development, Release

4. Experience Relatively smooth transition Some difficulties with old clients: simple “solution” found  always use https. Example: svn co https://alisoft.cern.ch/AliRoot/trunkhttps://alisoft.cern.ch/AliRoot/trunk Need for a conversion table “SVN for CVS users”

5. Plans Use the advanced features (see the red lines on the proposal slide) Install additional monitoring tools: statsvn Update the “Offline bible” replacing all the CVS examples by the corresponding SVN ones Prepare “SVN for CVS users” Include short SVN section in the tutorial slides Rearrange the modules including new subdirectories for the summer AliRoot release Collect more feedback from the users