Automate Lightning Beta Releases

RESOLVED FIXED

Status

RESOLVED FIXED
8 years ago
a year ago

People

(Reporter: Fallen, Unassigned)

Tracking

Details

The release automation used for applications doesn't really work well for Lightning, there are too many special cases. It might be better to create special automation using extensionfactory.py that takes Lightnings special cases into account.
Using this bug as a meta-bug to track things needed to create automated beta builds. Please see dependent bugs.
Depends on: 673083, 673086, 656350, 669082
No longer depends on: 635740
Summary: Create specialized release automation for Lightning → Automate Lightning Beta Releases
Depends on: 681776

Comment 2

8 years ago
Fixing https://bugzilla.mozilla.org/show_bug.cgi?id=401779  would eliminate the need for these separate "automation" and "updating" processes.
(In reply to Worcester12345 from comment #2)
> Fixing https://bugzilla.mozilla.org/show_bug.cgi?id=401779  would eliminate
> the need for these separate "automation" and "updating" processes.

But it wouldn't fix the "missing-strong-module-owner-for-each-area" problem.

Comment 4

5 years ago
Any chances of finalizing this bug?
Sure thing! I don't think we have to do anything here anymore. The build process is handled by Thunderbird and all thats left is bug 656350 which is just an enhancement to what I am doing now.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Comment 6

a year ago
(In reply to Philipp Kewisch [:Fallen] from comment #5)
> Sure thing! I don't think we have to do anything here anymore. The build
> process is handled by Thunderbird and all thats left is bug 656350 which is
> just an enhancement to what I am doing now.

Thanks. Do you have a link to the code that was fixed here? I think it is called a differential.
?
The code is in the various dependencies for this bug
You need to log in before you can comment on or make changes to this bug.