Manage Learn to apply best practices and optimize your operations.

Enterprise release management: The top 10 myths

Kevin Parker
Serena Software
7/11

Some changes happen too fast for software release testing? Wrong!

Source:  Getty Images/Fuse

Every code change needs to go through some process of release testing, verification and approval. It doesn't necessarily mean that every change goes through the exact same release-testing process. Emergency fixes needs a fast-track testing process with minimal stage gates and approvals. Major releases need more rigorous software-release testing processes and more complete stage gates.

View All Photo Stories

Join the conversation

2 comments

Send me notifications when other members comment.

Register

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Certain things do require specific amount of time and a skillset, and there are no shortcuts unless you change the context. If deployment and roll back process is fast and effective, a company may have a luxury of releasing less tested builds because they pull back and fix them swiftly. And if the application does not serve really important functions.
Cancel
Certain things do require specific amount of time and a skillset, and
there are no shortcuts unless you change the context. If deployment and
roll back process is fast and effective, a company may have a luxury of
releasing less tested builds because they pull back and fix them
swiftly. And if the application does not serve really important
functions.
Cancel

-ADS BY GOOGLE

SearchMicroservices

TheServerSide.com

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchHRSoftware

SearchHealthIT

DevOpsAgenda

Close