| ||||||||||||
 Trade In this Item for up to £0.25
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Pragmatic Version Control: Using Subversion (Pragmatic Programmers) for an Amazon.co.uk gift card of up to £0.25, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Product Description
This book covers the theory behind version control and how it can help developers become more efficient, work better as a team, and keep on top of software complexity. Version control, done well, is your "undo" button for the project: nothing is final, and mistakes are easily rolled back.
This book describes Subversion 1.3, the latest and hottest open source version control system, using a recipe-based approach that will get you up and running quickly and correctly. Learn how to use Subversion the right way-the pragmatic way.
With this book, you can:
- Keep all project assets safe--not just source code--and never run the risk of losing a great idea
- Know how to undo bad decisions--even directories and symlinks are versioned
- Learn how to share code safely, and work in parallel for maximum efficiency
- Install Subversion and organize, administer and backup your repository
- Share code over a network with Apache, svnserve, or ssh
- Create and manage releases, code branches, merges and bug fixes
- Manage 3rd party code safely
- Use all the latest Subversion 1.3 features including locking and path-based security, and much more!
Now there's no excuse not to use professional-grade version control.
From the Publisher
This book is a recipe-based approach to using Subversion that will get you up and running quickly---and correctly. All projects need version control: it's a foundational piece of any project's infrastructure. Yet half of all project teams in the U.S. don't use any version control at all. Many others don't use it well, and end up experiencing time-consuming problems.
Version Control, done well, is your "undo" button for the project: nothing is final, and mistakes are easily rolled back.
This book describes Subversion 1.3, the latest and hottest Open Source version control system.
Learn how to use Subversion the right way---the pragmatic way.
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
18 of 18 people found the following review helpful
Format:Paperback
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!
14 of 14 people found the following review helpful
Format:Paperback
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.
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.
5 of 5 people found the following review helpful
Format:Paperback|Amazon Verified Purchase
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.
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.
Would you like to see more reviews about this item?
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
