Chapter 16 - Code Releasing

=======================

16.1 Introduction
When a game is code released, it means the content is final, the bugs are addressed, and the master
version of the game is ready to be replicated and distributed.

The code release process will involve daily meetings to discuss bugs, a code release checklist, procedure
for submitting to a third party for approval, and information on where to send the code for replication
and distribution.

The code release process can take anywhere from five days to two months, depending on the
complexity of the game and who needs to approve it.

16.2 Determining Code Release

Define a code release process so that the development team and QA department are in agreement
about when a game is ready for code release or third-party submission.

Check the code release candidate against the entire test plan and the technical requirements checklists
and other third parties.

This is an ideal time to double check that the copyright and other legal information is correct, that all the
appropriate age ratings have been secured, and that the localized versions of the game have been
approved by the appropriate people.

The main purpose of the code release process is to fully verify that the final version of the game that is
going to be commercially distributed contains all the correct code and assets.

A code release candidate (CRC) is a version of the game that has addressed all the bugs, has all the final
assets, and is deemed ready to ship by the development team. A game may have several CRCs during
the code release process in order to address any major issues that are uncovered.

Any game appearing on proprietary hardware such as a console or mobile device must be submitted to a
third party for approval.

16.3 Code Release Checklist

Create a code release checklist to ensure that code release requirements are clearly defined and
understood.

Additional information that should be double-checked as well:

• Copyright information
• End user license agreements
• Licensor approval
• Customer support information
• Localized assets
• Demos
• Software ratings
 • Third-party submission requirements

16.4 Gold Masters

The replication and distribution of gold masters for PC games will be handled directly by the publisher. If
the replication is releasing the game on disc, the publisher will select a replication vendor who will
create all the game discs. If the game is going to be digitally distributed via a platform like Valve's Steam,
the publisher will upload the final code to the appropriate area so it can be released into the digital
distribution channel.

Games that must be approved by third parties have one more step to complete before they can be
commercially released. An account manager is assigned to work with the developer and publisher, and is
responsible for guiding the game through the approval process.

The final approval process nedd to be shceduled and on average takes about 10 to 20 days, but you may
also need to submit the build for third-party approvals during the alpha and beta phase as well.

Packaging also needs to be submitted for approval. In most cases, the packaging has a submission
process that is separate from the gold master, and is handled by someone from marketing or creative
services.

As the project comes to a close, keep people informed of any changes to the code release schedule
because this will also affect the ship date.

16.5 Chapter Summary

The code release process is one of the most critical steps in developing a game. This is the point at which
the developer and publisher agree that the game has been thoroughly tested and is ready to be sent to
the manufacturer for replication and shipped to store shelves.

Source: The Game Production Handbook 3rd Edition 2014 by Heather Maxwell Chandler