Confirmed users
1,989
edits
mNo edit summary |
mNo edit summary |
||
| Line 58: | Line 58: | ||
I did this and reran the final_release_verification job. It failed because the update tests don't deal with the 38.0 and 45.0 split. I changed the balrog rules so the TB team could test updates on release-cdntest (from 38.x to 45.x) (removed version restriction and increased priority). Once they conclude their testing, we can set the balrog rule for release for 45.0 to remove the version restriction temporarily and set a low rate (10). (Rate was set to 10 on release channel on Friday morning, will set it to 0 on Friday night) | I did this and reran the final_release_verification job. It failed because the update tests don't deal with the 38.0 and 45.0 split. I changed the balrog rules so the TB team could test updates on release-cdntest (from 38.x to 45.x) (removed version restriction and increased priority). Once they conclude their testing, we can set the balrog rule for release for 45.0 to remove the version restriction temporarily and set a low rate (10). (Rate was set to 10 on release channel on Friday morning, will set it to 0 on Friday night) | ||
* Friday at 5pm ET - set the rate back to 0 and Version to > 45.0 for the release channel for tb 45.0 | * Friday at 5pm ET - set the rate back to 0 and Version to > 45.0 for the release channel for tb 45.0 | ||
* Tuesday Apr | * Tuesday Apr 19 at 5pm ET - * allow updates from version 38 to 45, but keep background rate at 0 | ||
* Wed Apr 20 at 4pm ET - set background rate to 10 | |||