For those who don't know, we've been in the process of developing the next release of the Subversion version control system for almost 2 years. During that time, lots of new features, including the primary feature of merge tracking, have gone into trunk. Two weeks ago, the development team created the 1.5.x release branch, to begin stabilization for a 1.5.0 release. The branch is considered "feature complete", and we'll soon start cutting release candidates from it.
Until the time we cut the first release candidate, people eager to test 1.5 can check out the nightlies page, where they can download the latest and greatest code from the 1.5.x release branch. Of course, the code is completely untested and not formally released, so please, please don't use it on data you can't afford to lose. As always, bug reports and comments should be submitted on the Subversion homepage.
6 years ago
2 comments:
Not that I looked carefully over the latest features in 1.5, but the one feature that would be killer would be local commits. Lemme explain.
Suppose you are working on subversion's code from somewhere where you don't have internet. You should be able to keep track of your personal revisions without having to connect back to the server.
This sort of personal revision keeping is what makes distributed version control systems like GIT popular.
I agree. Local commits are a feature that I (and at least a couple other developers I know of) have wanted for a while. For disconnected development, or even code experimentation, local commits are a great way of using version control tools, but still keeping the changes private. Distributed systems excel in this arena.
Personally, I see Subversion eventually supporting a hybrid model. There would still be the One True Server, which houses the authoritative version of the code, but commits to could be made locally, and then shipped up to the server when desired. It would also be useful to keep more than just one revision's worth of history on the client, which is also a distinguishing feature of distributed version control systems.
Post a Comment