[livesupport-dev] Subversion Conversion
  • Vote Up0Vote Down importimport
    Posts: 0Member
    I've tested the conversion from CVS to subversion and everything seems
    to work fine. It is possible to just convert one project to subversion
    (e.g. campsite), but there are also advantages to moving everyone to
    subversion because you can copy files across projects and keep the
    history.

    I've tested TortoiseSVN on windows and it works very well. For linux I
    have only tried the command line so far. Both work using SSH, but I'm
    not sure if we want to go this route since it asks you to type in your
    password a lot (unless you install SSH-AGENT, a process that seems to
    involve voodoo and witchcraft).

    It will take a day of downtime (probably less, but I want to be
    conservative) to do the switch. Before this, all outstanding files must
    be committed to CVS, otherwise you will have to manually merge them once
    the switch is complete. You will also have to learn a little bit about
    subversion, but almost all the commands are the same as CVS. The main
    thing you will have to learn is how branching is different in Subversion
    (I can explain this later, after we decide on the switch).

    LiveSupport developers: do you want to do the switch, and if so, what
    day would work best?

    Sava and Doug: are there any other projects in active development right
    now? If so, who do I contact?

    - Paul

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • 1 Comment sorted by
  • Vote Up0Vote Down importimport
    Posts: 0Member
    Paul Baranowski wrote:
    > I've tested the conversion from CVS to subversion and everything seems
    > to work fine. It is possible to just convert one project to subversion

    good to hear that migration is easy...

    > (e.g. campsite), but there are also advantages to moving everyone to
    > subversion because you can copy files across projects and keep the history.

    yes, there are a lot of advantages over CVS in subversion...

    > I've tested TortoiseSVN on windows and it works very well. For linux I
    > have only tried the command line so far. Both work using SSH, but I'm
    > not sure if we want to go this route since it asks you to type in your
    > password a lot (unless you install SSH-AGENT, a process that seems to
    > involve voodoo and witchcraft).

    but, you could work around that. also, you can use HTTPS for subversion,
    I tried such a setup, and it was working quite fine...

    > It will take a day of downtime (probably less, but I want to be
    > conservative) to do the switch. Before this, all outstanding files must
    > be committed to CVS, otherwise you will have to manually merge them once
    > the switch is complete. You will also have to learn a little bit about
    > subversion, but almost all the commands are the same as CVS. The main
    > thing you will have to learn is how branching is different in Subversion
    > (I can explain this later, after we decide on the switch).

    let me also point out for non-technical people, that ToroiseSVN is a
    extremely easy Windows client, basically integrates into your Explorer,
    and lets you work from there...

    > LiveSupport developers: do you want to do the switch, and if so, what
    > day would work best?

    well, I'd be quite eager to switch. but: after our 1.0 release, which
    means after SummerCAMP


    Akos

    ------------------------------------------
    Posted to Phorum via PhorumMail
Add a Comment