Q
Problem solve Get help with specific problems with your technologies, process and projects.

Ensuring stability of beta releases

John Robbins
Wintellect
Follow:
We are having trouble with the stability of our beta releases. Do you have any hints on how we can ensure we get better stability?
One of the most important things I do when scheduling projects is to impose a two-week code freeze. The big mistake many people make is that they only schedule one week for code freeze when they hit a milestone. In that week you are attempting to fix bugs, which destabilizes the code base considerably. My trick has been to schedule a two-week code freeze. The first week is absolute feature freeze with only bug fixes allowed. If developers are not fixing bugs, they are testing that week. The second week is complete code freeze where you are not changing the code at all. Of course, you have to fix any show-stopper bugs, but the key is that you are getting the best testing effort on the actual bits you are shipping to your customers.
This was last published in January 2001

Dig Deeper on Windows Operating System Management

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Meet all of our Windows Server experts

View all Windows Server questions and answers

Start the conversation

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.

-ADS BY GOOGLE

SearchServerVirtualization

SearchCloudComputing

SearchExchange

SearchSQLServer

SearchEnterpriseDesktop

SearchVirtualDesktop

Close