Daily Build Thread 2015-05-09 Through 2015-05-15

[JoeS]

Daily Build Thread
[If you would like to volunteer to post this weekly thread on a rotational basis
Please go here: http://wiki.mozilla.org/Thunderbird:Nig ... ld_Threads for further instructions.]

Links
RSS feed Compliments of FB|PuppetMaster..Thanks
Calendar Versions
Today's Bugs

Danger, Will Robinson, danger!
Current situations to be aware of

No Critical Situation At This Time

Checkins This Week

Now posted in each channel's status section

Recent Bugs/Links of interest

Latest Tested Builds

The current nightly build, unless otherwise noted

Thunderbird-Beta Thunderbird 38.0 / Gecko 38.0 Status

Green


Latest-candidates:38.0b1-candidates
Treeherder l10n Dashboard
Tinderbox_Builds_win32

Checkins This Week
Click on the Treeherder link above to view Checkins

Earlybird Thunderbird 39.0a2 / Gecko 39.0 Status

Green

Latest-Nightly Links en-US l10n
Treeherder l10n Dashboard
Tinderbox_Builds_win32

Checkins This Week
Click on the Treeherder link above to view Checkins

Daily Thunderbird trunk 40.0a1 / Gecko 40.0 Status

Open

Latest-Nightly Links en-US l10n
Treeherder l10n Dashboard

Checkins This Week

Click on the Treeherder link above to view Checkins

[rsx11m]

Merge day...

[rsx11m]

Merges are done, except for comm-esr38. Instead, a 38.0b5 has been tagged on comm-beta.
Thus, it doesn't look like the 38.0 release is going to happen tomorrow.

[Mouse5]

Merges are done, except for comm-esr38. Instead, a 38.0b5 has been tagged on comm-beta.
Thus, it doesn't look like the 38.0 release is going to happen tomorrow.

the Firefox Team made a RC2 for just 1 dy. so my guess they did the same with TB38 so the release will go as Scheduled IMO

[rsx11m]

Maybe, but this is a beta from comm-beta, and they yet have to merge that branch into comm-esr38 and build 38.0 final from it and sign it and push it to the mirrors, etc. In contrast, once you have a true release candidate (not just a beta) it's mostly a matter of the very last item (push that build to the release side).

Well, it's always good to stay optimistic!

[patclash]

Merges are done, except for comm-esr38. Instead, a 38.0b5 has been tagged on comm-beta.
Thus, it doesn't look like the 38.0 release is going to happen tomorrow.

from tb-planing mailing list :

Thunderbird 38.0 will not ship on the same date as Firefox 38.0 but will
likely be delayed a couple of weeks.

We are approaching the originally scheduled date of the release of
Thunderbird 38, which would be May 12 following the standard Mozilla
release calendar. But there are still a number of regressions that we
are working on, and last week's beta was the first beta that was feature
complete. That means we will not be ready to ship according to the
original schedule. A current estimate of when we will ship Thunderbird
38.0 is approximately May 26.

Until we are ready to ship a finished Thunderbird 38.0, we will continue
to ship betas of Thunderbird 38 to the beta channel.

We'll do a new beta of Thunderbird 38.0 this week. At this point
mozilla-esr38 has diverged from mozilla-release, and it is mozilla-esr38
that is the correct channel for us to follow. So we will do future betas
of Thunderbird 38 from comm-esr38 and mozilla-esr38 (on branch
THUNDERBIRD_38_VERBRANCH) unless there are unforeseen technical issues.

A 38.0 Beta 5 is on the road :
https://ftp.mozilla.org/pub/mozilla.org ... es/build1/

[Bozz]

Update. Builds possibly tomorrow... or not. Depends on what happens.

2015-05-11 16:46:38 EDT

> Branch uplift took place today and now the fix is not available on
> comm-aurora anymore. Up to now no new broken 41.0a1 or 40.0a2 builds with
> Lightnings application.ini exists on the server. Maybe use the chance and
> re-apply the patch to ensure that the next successful nightly builds will
> not introduce the same problem again?

2015-05-12 02:34:36 EDT

> Pushed to central and aurora so we have it on all branches.
>
> https://hg.mozilla.org/releases/comm-au ... 0abd44e250
> https://hg.mozilla.org/comm-central/rev/d1979f04df5a
>
> I bet we could get releng to do some deletes, but I'm not sure how that will
> affect the update server. I'll see if I can either push forward the patch to
> fix it in the build system or get releng to do soemthing else about it.

[HN_FIN]

It is actually rather sad that there have been no Thunderbird nightly/aurora builds for the major platforms for two weeks. And devs seem to be a bit uncertain about the reason and fix. Building a new version is apparently so tightly tied to the previous version that a missing "correct" previous version kills the whole build, not just the "small update" .mar file

[rsx11m]

It is actually rather sad that there have been no Thunderbird nightly/aurora builds for the major platforms for two weeks.

Still better than SeaMonkey, which hasn't seen Windows nightly builds for three release cycles now and had to scrap 2.34 due to build-system issues...

[Bozz]

Builds possibly tomorrow... or not.

... not.

[rsx11m]

Good that 38.0 hasn't been released yet. Firefox 38.0 has been pulled from the release channel again as a typo in a DLL made Windows builds crash in certain circumstances (always funny that such things aren't caught before the release is released, especially if someone points out that the bug still occurred in a beta?).

[Mouse5]

Thunderbird-Beta Thunderbird 38.0 / Gecko 38.0 Status http://ftp.mozilla.org/pub/mozilla.org/ ... es/38.0b5/

Earlybird Thunderbird 39.0a2 / Gecko 39.0 Status now is Earlybird Thunderbird 40.0a2 / Gecko 40.0 Status

Daily Thunderbird trunk 40.0a1 / Gecko 40.0 Status now is Daily Thunderbird trunk 41.0a1 / Gecko 41.0 Status

[Bozz]

Nightly builds ran today.

The addons manager shows a warning on each addon that it could not be verified for use in Daily, Proceed with caution.
Addons/Extension Signing

I'm not positive but I believe I saw some comments somewhere that addon signing would not be required for Thunderbird and SeaMonkey. I don't know if there is a relevent bug report out to remove that requirement.

[Bozz]

Looks like this bug to remove addon signing requirement...

Bug 1164168 - RFE: mozconfig option to disable unsigned addon warning at build time for non-Firefox applications

[rsx11m]

Yes and no, that's for removal of the warning when the signing requirement is not enforced (as should be the default for any non-Firefox build).