Bug #10753

Investigate release timing of Icedove

Added by Anonymous 2015-12-14 06:26:06 . Updated 2016-05-10 04:34:37 .

Status:
Resolved
Priority:
Low
Assignee:
Category:
Target version:
Start date:
2015-12-14
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:
268

Description

  1. What’s the plan regarding having MFSA’s fixed in Icedove when we release a new Tails? In other words: will we always be lagging behind security updates in Icedove by N weeks, or can we do better?
  1. Does upstream release a new Thunderbird at the same time as the new Firefox?
    See:
    https://www.mozilla.org/en-US/thunderbird/releases/
    https://www.mozilla.org/en-US/firefox/releases/
    https://wiki.mozilla.org/Releases
  1. How fast does it flow into Debian?
    See https://tracker.debian.org/pkg/icedove

Subtasks


History

#1 Updated by Anonymous 2015-12-14 06:51:24

  • Description updated

#2 Updated by Anonymous 2015-12-14 06:53:46

  • Description updated

From what I see there does not seem to be a strict release timing for Thunderbird although often new versions get released at the same time as Firefox versions.

These versions seem to land in Debian unstable about a week later and in testing 5 more days later.

I have asked the DDs who take care of the package to confirm this, because I had a rather quick view, evaluating only the latest releases.

#3 Updated by Anonymous 2015-12-14 06:54:08

  • Status changed from New to In Progress

#4 Updated by Anonymous 2015-12-14 06:55:53

On https://wiki.mozilla.org/Releases, in the upcoming release section, only the releases marked as “moves to RELEASE” seem to be relevant for us as not BETA releases.

#5 Updated by Anonymous 2015-12-14 07:05:46

  • Description updated

#6 Updated by Anonymous 2015-12-14 07:06:32

  • Description updated

#7 Updated by intrigeri 2015-12-14 07:28:44

  • Deliverable for set to 268

#8 Updated by Anonymous 2015-12-14 07:57:17

About MFSAs, they seem to be quite rare (november 2015, and before august 2015 for the last ones).

#9 Updated by Anonymous 2015-12-14 08:39:29

  • Target version set to Tails_1.8

#10 Updated by Anonymous 2015-12-14 08:39:40

  • Target version changed from Tails_1.8 to Tails_2.0

#11 Updated by Anonymous 2015-12-15 04:32:48

I’ve gotten quite a detailed answer from the Debian maintainers.

>> * Does upstream release a new Thunderbird at the same time as the new
>> Firefox?

Mostly but not necessary. The last releases of Thunderbird was always
delayed after the Firefox release. For example right today there was FF
43 released but Thunderbird will take some more days.

http://download-origin.cdn.mozilla.net/pub/firefox/releases/
http://download-origin.cdn.mozilla.net/pub/thunderbird/releases/

>> * How fast does it flow into Debian?

There we have to make some difference between experimental/unstable and
[old]stable-security.
For experimental and unstable I'm trying to be much as close to the
official release. It my happen within a few days, but sometimes it can
also take up two or three weeks. Problem is not Thunderbird only, but we
want to provide the language packages also. They are currently handled
by separate packages. But we plan to consolidate the packages.

[old]stable-security is done by Christoph, mostly near by the release of
Mozilla. New ESR versions take some more time due porting problems like
happen with 38.3. and 38.4.

Intrigeri & Anonym suggested that we might try to help the Debian folks to get the new upstream versions quicker into the Debian Vcs-Git so that we (Tails) might build our packages in time. In exchange this would help the Debian folks with QA relying on our build.

Discussion follow-up on tails-icedove I hope.

#12 Updated by Anonymous 2015-12-15 04:33:12

  • % Done changed from 0 to 20

#13 Updated by Anonymous 2015-12-17 08:29:07

Follow up discussion/thread and more details: https://mailman.boum.org/pipermail/tails-icedove/2015-December/000098.html

Getting the new upstream versions to Git is not much of a problem, but from what I understand, the things that take longer are:

  1. the person doing most of the work is not a DD and cannot upload things himself
  2. there is a huge patchset which has not been upstreamed and help would be required on this issue

I am not sure how much we are capable to help with 2., mostly because we lack time & work force.

#14 Updated by Anonymous 2015-12-17 08:29:49

  • Priority changed from Normal to Low

Setting priority of this ticket to “low” as the discussion has been started and we simply need to keep it going.

#15 Updated by Anonymous 2016-01-12 16:08:40

  • Status changed from In Progress to Resolved

I think it’s clear now that we’ll simply stick to the Firefox/TBB release schedule and treat Icedove exactly in the same way as other software we ship.

#16 Updated by intrigeri 2016-05-10 04:34:37

  • Assignee deleted ()
  • % Done changed from 20 to 100