Available from 8 stores - Select your deal and buy the Software Release Methodology
"Where can I buy a Software Release Methodology?" At all of these merchants listed below. Click any of the deals below to buy now on the merchant's website.
Absolutely Brand New & In Stock. 100% 30-Day Money Back. Direct from our warehouse. Ships by USPS. 1+ million customers served-In business since 1986. Happy Customers is Our #1 Goal. Toll Free Support
Latest 6 Reviews Here is what people are saying about the Software Release Methodology
"For me it was a waste of money"
2007-04-23
- Reviewed By User: A2EYOQ2TKS87F5
This book is very dense, both in layout and writing style. It is long on verbose discussion and short on practical examples and advice. For example there 24 pages on release version numbering but only 8 pages on revision branching and merging.
The layout would have benefited from lists and more diagrams. It would also have been useful to have more example templates and processes.
What also annoyed were the basic mistakes e.g. How to correctly number a branch revision (it should normally be parentRev.BranchNumber.RevisionOnBranch, not parentRev.RevisionOnBranch).
I think the editors must take a significant portion of the blame for failing to help the author deliver a more readable book
Just received this book after waiting 2 months for it. I purchased it because it is often referenced in other CM books.
After just scanning through the book, I can tell that it contains some valuable information. One big minus is the index consists of blank pages, which is really bad for a technical book.
The physical quality of the book is very poor. Cheap binding, cheap paper, cheap type. Except for the nice cover, it looks like it was thrown together at Kinkos.
What really irks me is that I paid almost $50 for this book. This is something I would pay $10 for a PDF download.
Excellent details for SCM/CM strategies. Starts off with a couple of chapters for beginner's to SCM. Then covers every aspect of Release Process. The chapter on integration process was detailed like no other SCM book that I've seen. The book explains concepts of software development from the perspective of a Release Engineer -- from source control branching/merging strategies, to build control, aspects of development cycle, then to product release. One of the better CM SCM books out there. None of the others SCM books look at it from a Release Engineer's perspective like this one. If you are already passed the basics of SCM then this book will complete your training.
"I have only skimmed through this book, but"
2004-08-13
- Reviewed By User: A2D47MB7G6LKNH
Have you noticed that in a book about release methodology, they have forgotten to release a part of the book? There is a title, it's in the TOC, and a few pages even serve as a placeholder, but the Index is simply missing. At least in my copy of the book... oops.
I went out and got a copy of this book because (1) relatively good initial reviews, (2) the items in the Table of Contents that made sense. Although the content does not suck as badly as what the other reviews wrote, it wasn't "satisfying". Bays placed in sections of text assuming the readers do not an inkling of a tech background, and no idea whatsover on the psychology of a software shop. It's nice to see in print all the psychological/organization behavior assessments you've made through years of painful lessons, but I needed a book that will tell me practically what to do (or at least a story about what worked for him and what he thinks one should do in different set ups). No, instead he launches into a textbook style discussion of a lot of basics with the assumption that the reader have never gotten been down in the trenches as a /with the developers before.
It's not an entirely bad approach. Like I said in the title of this review, this book is great for "Pointy Haired Managers" (ala Dilbert) -- managers of tech organizations who have never been in the trenches himself. No sarcasm intended. It's also a good book to use when you have to educate/convince "Pointy Haired Managers" on how things "should be" done (because it sounds really illogical from his simplified point of view). No sarcasm intended here too. (Those who have worked with non-technical bosses will agree with me the hardest part is educating a boss with a slight tendency to micromanage -- because he couldn't grasp the situation.)
Actually this book can be a great text book for an IT Technical Management course for non technical managers. It does have everything you need to know about the last stages of software development (THE RELEASE).
"Contains trivial facts everybody knows"
2002-01-16
- Reviewed By Anonymous
I bought this book, because of the great reviews, but I must agree with the comment "If you know ANYTHING about developing software...ANYTHING at all...this book is a complete waste of time." Area of release planning IS interesting and difficult, but solution is not this book.
Last updated: Nov 22, 2009 at 10:15 EST. Pricing information is provided by the listed merchants. GoSale.com is not responsible for the accuracy of pricing information, product information or the images provided. Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on amazon.com or other merchants at the time of purchase will apply to the purchase of this product. As always, be sure to visit the merchant's site to review and verify product information, price, and shipping costs. GoSale.com is not responsible for the content and opinions contained in customer submitted reviews.
International Available
"For me it was a waste of money"
"Good Information, Poor Quality"
"Software Release explained in detail"
"I have only skimmed through this book, but"