Daily Build Thread 2015-09-12 Through 2015-12-11

[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

[*]#1193200 [Thunderbird:Message Reader UI]-Remote content exceptions: Cannot add email address to blocklist with Block and Allow buttons; adding web site seems to succeed but also invisible [All]

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 41.0b2 / Gecko 41.0 Status

Green


Latest-candidates:41.0b2-candidates
Treeherder l10n Dashboard
Tinderbox_Builds_win32

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

Earlybird Thunderbird 43.0a2 / Gecko 43.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 44.0a1 / Gecko 44.0 Status

Green

Latest-Nightly Links en-US l10n
Treeherder l10n Dashboard

Checkins This Week

Click on the Treeherder link above to view Checkins

[JoeS]

I have renewed the thread from the last post to the next 30 days

Beta 41b2 is released with the hibernate bug fixed (and It's not even October yet )
Relnotes are Here

It seems like a very fine build

[rsx11m]

... and again - merge day!

[wsmwk]

42.0b1 is on hold regarding Mac - possibly related to https://bugzilla.mozilla.org/show_bug.cgi?id=1199957

[toolong]

... and again - merge day!

I see, for Windows, a 42.0b1 (beta for what should be 38.4.0 someday. I see also Earlybird 43.0a2 as well as Daily 44.0a1 and they have been updating every day. But I have yet to see an update from release 38.2.0 to 38.3.0.

Am I missing something?

[wsmwk]

Pretty simple. Keep these in mind

Release builds for TB do not happen always per calendar
Rellease builds for thunderbird do not happen exactly lock step with Firefox

[toolong]

Pretty simple. Keep these in mind

Release builds for TB do not happen always per calendar
Rellease builds for thunderbird do not happen exactly lock step with Firefox

Well that is obvious, and has been for some time, but I just found it odd that the beta for the next release preceded the update/patched actual stable release of the current stable released program. I gather that you do not find that odd?

I find it truly sad that Mozilla pulled the plug for the resources on the Thunderbird project and let these few 'citizen developers' (true name??) twisting in the wind.

This release, for example, is supposed to solve the 'I don't phone home for email' bug and the only version that does *not* do that is the current, stable(??) release numbered 38.2.0. Which, as I said, was not been fixed.

Me? I find that odd.

[rsx11m]

Well that is obvious, and has been for some time, but I just found it odd that the beta for the next release preceded the update/patched actual stable release of the current stable released program. I gather that you do not find that odd?

No, it's not odd. Releases for Thunderbird actually come from the "Extended Support (ESR)" branch, which currently is 38.x (was 31.x before, 45.x will be the next). Thus, the recent beta release isn't actually a beta for 38.3.0, but towards 45.0 once that ESR branch ends.

The main oddity is that Firefox keeps up a fairly decent pace making changes to the common code, without much regard to how it affect other applications, thus Thunderbird and SeaMonkey have to keep up with those (which was the main reason for switching to the slower-moving ESR release branch to start with). So, give the devs some slack, will you?

[toolong]

No, it's not odd. Releases for Thunderbird actually come from the "Extended Support (ESR)" branch, which currently is 38.x (was 31.x before, 45.x will be the next). Thus, the recent beta release isn't actually a beta for 38.3.0, but towards 45.0 once that ESR branch ends.

Hmm. I see. I stand corrected. But. I still do not think that is the proper way to deal with updates.

Means? I, me, thinks it is wrong to update the trailers while the leader is still behind. It just does not feel correct. Why should the beta of the next potential release, some six months or so in the future, have a higher release number than the current stable release? To me? That just sounds wrong.

I am open for explanation(s) if you have the time.

[rsx11m]

I'm not sure if I understand correctly which problem you are seeing, but 38.2.0 was built 13-Aug-2015 and 41.0b1 on 09-Sep-2015, which correspond to the same cycle. Current beta is 42.0b1, which was built yesterday and thus indeed ahead of 38.3.0 which isn't even tagged yet, that's true. The betas undergo less QA than the actual releases, or it may be just a matter of build resources available, I don't know what the reason was to build the next beta ahead of the release. Frequently they are still waiting for a specific fix before tagging the next release, to avoid a quick "dot" release following up to fix a current issue.

[wsmwk]

I find it truly sad that Mozilla pulled the plug for the resources on the Thunderbird project and let these few 'citizen developers' (true name??) twisting in the wind.

You are mistaken that we volunteers are twisting in the wind - we are getting plenty of resources and help from Mozilla and employees. We are, after all, building on their systems and using their automation. And most of us have been around for years and worked in various capacities along side the Mozilla staff who built previous releases. On the whole we are doing relatively fine. Still learning new things on every go, but that is to be expected. (which is not to say we couldn't use more volunteers in EVERY capacity)

I'm not sure if I understand correctly which problem you are seeing, but 38.2.0 was built 13-Aug-2015 and 41.0b1 on 09-Sep-2015, which correspond to the same cycle. Current beta is 42.0b1, which was built yesterday and thus indeed ahead of 38.3.0 which isn't even tagged yet, that's true. The betas undergo less QA than the actual releases,

Actually we are doing the same QA for betas and *point* releases. However, when we approach major .0 versions the QA process is different.

or it may be just a matter of build resources available, I don't know what the reason was to build the next beta ahead of the release. Frequently they are still waiting for a specific fix before tagging the next release, to avoid a quick "dot" release following up to fix a current issue.

Indeed, you are on the right track. Every week, indeed every day, the set of circumstances changes - resources, state of the branches, patches that we may decide to wait for or investigate, issues related to building, personal schedules, failures found during QA, etc. Add to that last minute changes or delays in what Firefox is doing that impact us. You name it, it happens.

In short we do betas and releases in an order and timing which best serves our cirumstances and users. Unfortunately not everything will seem logical to those not in possession of the information driving each shipping situation.

[toolong]

In short we do betas and releases in an order and timing which best serves our cirumstances and users. Unfortunately not everything will seem logical to those not in possession of the information driving each shipping situation.

I see. Thanks to you all for the information and explanations.

And to be perfectly clear at no time did I mean any disrespect to any of the developers nor to make light of their efforts.

I got lucky. "Curiosity killed the cat." All I got was some answers.

[wsmwk]

no offense taken - just getting the info out there.

you seem to have a strong interest. I hope you contribute

[toolong]

no offense taken - just getting the info out there.

you seem to have a strong interest. I hope you contribute

Sadly the only 'programming' I have ever done was typing Commodore 64 programs from magazines and a little GWBasic many years ago. As well as a little simple scripting in Linux.

[tajkkj]

I too am interested in the progress of ESR 38.3.0. In particular, I understand it should have the fix for Bug 1196662 (the hibernation bug) which is also fixed in Beta 41b2. What is the status on 38.3.0? Is there a target release date yet? This is a serious usability issue.

Thanks,
Tim