Most Helpful Customer Reviews
|
|
16 of 16 people found the following review helpful:
5.0 out of 5 stars
Pragmatic best practices with version control!, 9 Aug 2005
At first this book seems unobtrusive next to some other 400+ page books on your bookshelf. However, don't overlook it... This book is really easy to read, has good theory coverage, is brimming with down to earth practical examples and has lots of best practices that one should be using. The first 150 pages give the reader an in-depth introduction to Subversion and common place version control theory and mechanisms. The last 50 pages cover the appendix dealing with installation, security, migration from dated versioning systems such as CVS, third party tools and last but not least a command summary and set of recipes. I took a complete day to read the book and try out the examples. Considering the price of the book and the time spent reading it, its return on investment is high. It certainly knocks the socks off some commercial products and training I've seen in the past. Really, this is one book I certainly recommend for Architects, Software Engineers and SCM specialists even if you're not using Subversion!
|
|
|
12 of 12 people found the following review helpful:
4.0 out of 5 stars
All you need to start version control, 22 Jun 2006
No idea what the first edition was like, but as of version 1.3, if you're looking to get up and running with Subversion, this book is a must buy.
This takes you through setting up a repository and the various tasks you'd probably want to carry out, in a simple step-by-step manner. The slightly trickier proposition of setting up the subversion server is also covered, with both Apache and SSH variations, as well as the more basic svnserve.
Beyond the simple recipes, there is also some helpful advice on 'agile' use of repositories: guidelines on how to arrange a project and deal with things like 3rd party code, and the use of branching and tagging for dealing with bug fixes and releases.
Of the three Pragmatic Starter Kit books, this is the one that delivers the most value for money. There is more substantial information here than the Pragmatic Automation book, and unlike JUnit, there are not many up to date or comprehensive Subversion tutorials on the net for free. While the official Subversion book is freely available from the svn website, compiling all the information presented here is far more time consuming.
If you're looking to start version control with Subversion, then buy without hesitation.
|
|
|
2 of 2 people found the following review helpful:
4.0 out of 5 stars
Good as both tutorial and reference, 22 Dec 2008
This book is a handy tutorial and reference for Subversion.
It includes a very useful section that describes the differences between different version control systems. So, if you are moving from a version control system that always uses file locking, or if you are moving from a version control system that applies revision numbers to each file rather than to the repository as a whole, this section explains the differences you will find when moving to Subversion.
It explains all of the common tasks that you do when using a version control system, providing command summaries and examples for each. It also provides recommendations about how to organise your repository/directories and how/when to use branching and tags. It even goes so far as to recommend naming conventions for branches.
With sections on administering the repository, migrating to Subversion, third-party tools (including GUIs) that work with Subversion etc, this book covers almost everything you need to know. I still had a couple of questions outstanding when I finished the book, but those related to things that are very uncommon tasks, so easily missed out of a book of this size.
Note that the vast majority of this book uses the Subversion command-line, so for those people who don't like to move outside of a GUI the emphasis may not be quite what you want. However, the underlying principles are still things you need to know so I'd still recommend this book.
Some companies insist of their developers being "certified" in particular programming languages before being allowed to work on particular projects. On large projects it's inevitable that you will have developers of differing standards, so personally, I'd say it was even more important that the developers understood and used version control properly than be formally certified in a particular language. At least that way, there is some chance of monitoring and controlling the code that they produce, whatever the standard. If you cannot reliably and reproducibly produce a build based on code from version control, if you cannot relate source and documentation, if you cannot relate source and related test harnesses, if you cannot relate code to a released executable, what chance is there of anything working? Understanding version control is vital and this book is a good way of getting that understanding, particularly for those using Subversion.
|
|
|
Most Recent Customer Reviews
|