If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Disable partials for Thunderbird 38.0.1 -> 38.1.0 in balrog

RESOLVED FIXED

Status

Release Engineering
Releases
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Fallen, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
9:26:40 PM - Fallen: during which part of the release process are the .mar files uploaded to balrog? Is there a way to not upload or disable a certain partial even though it was built, or do we have to respin?
9:27:08 PM - bhearsum: Fallen: MARs don't get uploeaded to balrog
9:27:28 PM - bhearsum: we could strip out a specific partial from the metadata in balrog
9:27:58 PM - bhearsum: so no, you don't need to respin
9:28:15 PM - bhearsum: please file a bug and cc me, i'll take care of it tomorrow


Due to bug 1175063, Lightning did not get included in Thunderbird 38.0.1 for people updating from Thunderbird 31. Now updates Thunderbird 31 -> 38.1.0 work, but partial updates 38.0.1 -> 38.1.0 will still not include Lightning.

The easiest way to solve this would be to disable the partials for 38.0.1 -> 38.1.0, because then the complete update kicks in. I've verified this will get Lightning installed by manually applying the .mar files.

I am not sure when exactly the metadata gets uploaded to balrog, right now we just completed the candidate builds. If it's too early let me know.

tl;dr; please remove the metadata for thunderbird-38.0.1-38.1.0.partial.mar, for all platforms and locales.
This is done - you should be able to verify it by checking for updates with a 38.0.1 build on the release-localtest channel.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Final verify failed because of this, I had to fix up those configs by hand: https://hg.mozilla.org/build/tools/rev/6a74f8db36fb
You need to log in before you can comment on or make changes to this bug.