Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Mark Levison and Deborah Hartman on Jun 24, 2008 01:00 AM
Subversion is a mature open source version control system used by many open source projects, including Apache Software Foundation, KDE, GNOME, Free Pascal, GCC, Python, Django, Ruby, and Mono. Its developers have just released version 1.5. Subversion is version control system originally designed to replace CVS, which many felt had important limitations.
Although Subversion did provoke a "branching model" war in some quarters, it also brought significant improvements over CVS, according to some practitioners:
Subversion can use the HTTP-based WebDAV/DeltaV protocol for network communications, and the Apache web server to provide repository-side network service. This gives Subversion an advantage over CVS in interoperability, and provides various key features for free: authentication, wire compression, and basic repository browsing. However, Subversion also offers a "svnserv" standalone server option using a custom protocol, and can be tunnelled over ssh. And, although it is open source software, commercial support is available.
The Big Picture from the Subversion Developer Intro
Version 1.5 introduces a number of new features, among them:
A new version the Eclipse plugin for Subversion (Subclipse) has also been released. Other clients include: TortiseSVN (a windows shell extension), RapidSVN (a rich client) and AnkhSVN (a Visual Studio plugin).
5 Ways to Ensure Application Performance
Ebook: Scaling Agile with C/ALM
Ensuring Code Quality in Multi-threaded Applications
Checked-out directories are 'clean' (no CVS directories).
This is just plain wrong, there are those pesky ".svn" directories all over the place. So what if they renamed them from CVS to .svn ?
File caching allows more actions in "disconnected" state.
There is no "connected" state in CVS either, and "more actions" does not include checking the file log for example. So it's not really fully working disconnected, like Git does for example.
Sparse checkouts: allows developers with very large source trees to get only subsets of their code to their machine.
This is a misleading description. Developers with very large source trees need to keep their source trees separated in different directories, and subversion always allowed to get just one directory. The new sparse feature allows non-recursive checkout, when you only want part of a directory but not all of it.
This release is a step closer for Subversion towards becoming a true open-source clone of Perforce. Only thing left is a nice GUI.
For running Subversion on Windows also consider the tools provided by VisualSVN. There is the free VisualSVNServer for no-pain Svn administration and the commercial VisualSVN Visual Studio.NET plugin.
Evgeny - I'm sorry you find this article mis-leading. The first two items you remark on come straight from the SVN site (or the docs). The final point about sparse checkouts is my own mistakes. After twenty minutes of reading what was on the 1.5 release notes that is what I took it to mean.
As for an open source version of Perforce - I really can't see what its missing. Trust me its not the GUI. I use perforce on daily basis and neither of the Perforce GUIs (P4V or P4WIN) can be considered good. The only thing that saves it for day to day use is the Eclipse plugin. In addition Perforce's powerful mapping capabilities - i.e. the ability for each developer to map the same source tree into entirely different directory structures can make life hell. Often when I start coaching on a project the first thing I have to do is tidy up their client spec.
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
3 comments
Watch Thread Reply