Information Technology Reference
In-Depth Information
Chapter 8
Release Working
Software
Any Time,
Any Place
Label a
Repository's
Assets
Produce a
Clean
Environment
Label Each
Build
Possess
Capability to
Roll Back
Release
Create Build
Feedback
Reports
Run All Tests
If you want a thing done well, do it yourself.
—E
NGLISH PROVERB
If you are paid to write software, the organization that is paying you
most likely expects you to provide
working
software to end users after
a time span that is predictable and realistic. Therefore, it stands to reason
that our industry would have figured out a rock-solid way to deliver
high-quality, working software to end users on an expected schedule.
But still we hear the stories of the “nightmare release” that went hay-
wire, everyone was in a state of panic, lost sleep, got more gray hairs—
and still may not have resulted with the end user getting a new release.
Creating working software efficiently is the reason for a profes-
sional software developer's existence. Without a successful deployment,
the software doesn't even really exist. In today's world we create and
release software much more frequently, so we have to get that process
189
