# win32-win64 migration¶

These steps are meant to be specifically for Firefox and Devedition 56.0b9.

## High-level steps¶

1. Create a new release in balrog for the migration

2. Create a new balrog rule on the cdntest channels to point to to the release blob

## Detailed descriptions¶

After we have b9 release blobs available in balrog we need to create a new release in balrog for win64 migration. We also need to create a new watershed to map to this newly release in balrog so win32 users with certain criteria will be updated to win64 firefox. See bug 1393447 for more details.

## Creating a new release in balrog¶

1. Go to the Firefox release for 56.0b9

3. python munge.py /Users/kmoir/Downloads/Firefox-56.0b9-build1.json which creates Firefox-56.0b9-build1-win64-migration.json

4. In balrog add a new release where name is Firefox-56.0b9-build1-win64-migration and product is firefox

1. Add a rule to Firefox,beta-cdntest that points to that new rule. It should look like the top rule in this screenshot except it should be on the beta-cdntest rule. The mapping should be to b9 win64 migration release you just added. The buildid should be updated to reflect the b9 buildid in the release blob. The comment should say b9 instead of b7. You don’t require signoff for rules in test channels so it will just be added.

Devedition beta ~~~~~~~~~~~~~~-

## Modifying release blob¶

1. Go to the Devedition release for 56.0b9

3. python munge.py /Users/kmoir/Downloads/Devedition-56.0b9-build1.json which creates Devedition-56.0b9-build1-win64-migration.json

4. In balrog add a new release where name is Devedition-56.0b9-build1-win64-migration and Product is Firefox and upload your Devedition-56.0b9-build1-win64-migration.json file