The release migration view needs to support the following process: On merge day, - create a new AppVersion, with sign-offs enabled, per product -- this should be optional, at least temporarily - not require all branches to be part of the merge - for all enabled branches, migrate the previous appversion to this

Flod, this is how the team page will look after the second merge day, does that look right? I did change the ordering in the team page to make non-appversioned trees show last, too. The aurora trees will show until we disable them explicitly, added an item for that to the gantt.

Comment on attachment 8856953 [details] team page after second migration Not completely sure why Calendar is in that bucket, but the view in itself makes sense.

Commit pushed to develop at https://github.com/mozilla/elmo https://github.com/mozilla/elmo/commit/320e8a172e2afd8f96489ddc324936c9359d7767 bug 1355117, make branch optional during release migration This is how it works with dawn, when we want to take aurora out of the release migration. For the first merge day, we uncheck l10n-central, which migrates beta off of beta, aurora to beta, and leaves central alone, without creating a new appversion. On the next merge day, the UI only offers central and beta, and we can just keep every branch checked. In a future patch after dawn has settled, we should remove the aurora section.

FIXED and deployed in prod.