Slashdot Mirror

← Back to Stories (view on slashdot.org)

Subversion 1.5.0 Released

Posted by timothy on from the sand-in-the-gastank dept.

Hyrum writes "The Subversion team is proud to announce the release of Subversion 1.5.0, a popular open source version control system. The first new feature release of Subversion in almost 2 years, 1.5.0 contains a number of new improvements and features. A detailed list of changes can be found in the release notes. Among the major new features included in this release is merge tracking—Subversion now keeps track of what changes have been merged where. Source code is available immediately, with various other packages available soon."

3 of 104 comments (clear)

  1. Re:3, 2, 1 by cduffy · · Score: 5, Interesting

    Part of the problem is that the conversion scripts coming from CVS have to make up some data that isn't in the repository, but which all newer SCMs track.

    If you get yourself to something modern enough to support multi-file transactions, to recognize rename operations, to store merge history, and to manage branches in a reliable way (creating a file on a branch in CVS can also create that file in HEAD... or at least, it did last time I used CVS in production) future conversions won't be as necessarily painful and/or lossy.

    CVS isn't even reliable in terms of storing history in such a way that you can guarantee that you haven't lost something; when I was maintainer of cscvs, I had several users having problems because their ,v files had gotten truncated somewhere way back; because that only impacted attempts to retrieve revisions prior to the truncation point, nobody noticed until their backups had already been fully rotated past that point. More modern SCMs have provisions in their data formats for validating repository validity, and even for checking changesets against deliberate tampering.

    If you're legitimately concerned about your data, you'll get off of CVS at the first opportunity.

  2. Re:3, 2, 1 by truthsearch · · Score: 4, Interesting

    CVS was good enough for my company until we learned how SVN was able to make many things much easier. We did fresh imports of all of our projects into SVN. So we lost history in the new repository but kept around the old CVS repository just in case we needed its history.

    That was a few years ago and we're far more productive today, especially with branching and merging.

    --
    Developers: We can use your help.
  3. Upgrade breaks working copy compatibility by againjj · · Score: 5, Interesting
    There is an important piece that is going to keep me from being able to use it for a while:

    Before upgrading to 1.5.0, please take note of the following: * Due to various improvements made to the working copy library, the working copy format has changed. Using Subversion 1.5.0 on any working copy created by previous versions of Subversion will SILENTLY upgrade your working copy, which means that previous versions of Subversion will no longer be able to read it. I use multiple clients on my machine, and they all are going to need to be able to use 1.5 before any of them can.