Section 9.8. Checklist


9.8. Checklist

This section contains a short list of questions that you should feel comfortable answering about your own release process:

  • What's the next version number that your product will use? Who decides when it's time to make a change to each part of the version number?

  • Where do you go to find the latest public release of your product?

  • How large is the latest release of your product? Which part of the product creates most of the files that you deliver to your customers?

  • What other software does your product depend on, and which versions?

  • If your product needs license keys, where do you obtain these? How do customers obtain them? How long does it take for a customer to obtain a new license key?

  • What kinds of changes are allowed in a patch release? In a minor release? In a major release?

  • Which versions of your product will operate correctly with each previous version of your product? How does a customer know this?

  • Are a customer's data and configuration choices preserved when she upgrades your product?

  • Can a customer downgrade your product to an earlier version?

  • What's different between how developers run the product, how testers run the product, and how customers actually install and use the product? Have these differences been the root cause of any recent bugs?

  • If your product is available on the Internet, how does a customer prove that his downloaded package contains the same bits that you released?

  • What help do you have in your product for supporting it once it has been released? Can a customer easily display installation and configuration information, along with the results of any diagnostic tests? Can you use this as part of a phone call or in email?

  • How many releases can your group really work on at the same time?



Practical Development Environments
Practical Development Environments
ISBN: 0596007965
EAN: 2147483647
Year: 2004
Pages: 150

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net