Update a certified adapter

Changes to a certified adapter can occur for any of the following reasons:

When a change occurs that requires an update to your adapter, complete the following steps:

	Make the changes in the master branch of your adapter repository.
	Confirm that you've fulfilled our adapter code submission checklist, then log a pull request in GitHub against the `canary` branch. The `canary` branch is used for already-certified adapters to test their updates with publishers before merging to the stable `master` branch.
	Log a ticket with IX to request an update.
	We work together in a review cycle: IX reviews your code and may request changes. You make the code changes in your GitHub repository. This review cycle continues until we don't have any additional changes to request.
	We perform pre-production testing using a staging instance of a publisher's IX Library™. We provide you with access to the staging IX Library so that you can sign off on the testing. The publisher must provide us with their written permission to participate in this alpha test. You'll work with the publisher's IX Representative throughout the testing.
	Once we've received your sign-off on the testing, we can merge the updates to production and into the `master` branch on GitHub. Similar to the testing stage, we contact you to validate and sign off on the changes in production.
	After you've validated the changes in production, we mass launch the updates to all publishers, so that they're available to everyone. If any publishers want access to the update prior to the mass launch, ask them to contact their IX Representative so we can launch their IX Library.