|
|
(Larger Image)
|
Software Release Methodology
by Michael E. Bays
Product Group: Book
Publisher: Prentice Hall PTR (1999-07-03)
ISBN: 0136365647
EAN: 9780136365648
Dewey Decimal #: 005.0688
Paperback: 256 pages
SKU: 111808000333
Condition: New
Comments: 0136365647 New, never read, may have minor wear on cover.
|
Editorial Reviews
|
Product Description
Shows you best practices for every stage of a successful product release. Includes carefully designed, practical solutions that enhance quality, reduce costs, and get you to market faster.
|
Customer Reviews
|
For me it was a waste of money
Rating  (1)
Date: 2007-04-23
1 out of 1 customers found this reveiw helpful
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
|
|
Definitely not worth the money
Rating  (2)
Date: 2006-04-27
0 out of 1 customers found this reveiw helpful
If you are working for a company that makes software, chances are you have a guy who is assigned the task of release management. Do yourself a favor and go talk to this guy -- you'll probably get better insights than this book has to offer after draining $50 bucks out of your pocket. I only gave it 2 stars since the author touches on the right topics but fails to deliver useful content.
He delves into one specific style of release management and engineering (probably what the author's company does) and does not talk too much about alternate styles at all -- and the release methodology suggested by the book is less elegant than some of the release processes I've seen.
And as a bonus, a few blank pages serves as the index for the book. I was expecting better quality of content and presentation from Prentice Hall.
|
|
Good Information, Poor Quality
Rating (2)
Date: 2005-10-21
2 out of 2 customers found this reveiw helpful
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.
|
|
Software Release explained in detail
Rating  (5)
Date: 2005-06-14
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
Rating  (3)
Date: 2004-08-13
2 out of 5 customers found this reveiw helpful
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.
|
|
|
|
|