Bug 1414612 (ltn62)

Tracking bug for Lightning 6.2 release (Thunderbird 60)

RESOLVED FIXED

Status

enhancement
RESOLVED FIXED
2 years ago
8 months ago

People

(Reporter: MakeMyDay, Unassigned)

Tracking

(Depends on 4 bugs, {meta})

Lightning 6.2
Dependency tree / graph

Details

Meta bug for tracking 6.1

TB 59 goes to beta (= string freeze) at 2018-01-15.

I'm not carrying over any not fixed leftover blocking bug 1312113 automatically - this should be subject to an individual evaluation (to whether it is both, wanted and a reasonable target).
Depends on: 1299610
Depends on: 463402
If you make bugs block this meta bug, which need string changes, please add [has l10n impact] to the whiteboard of these bugs, so we could track all blocking bugs required until string freeze by this query:

https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=13865512&o1=casesubstring&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=%5Bhas%20l10n%20impact%5D&v1=1414612&product=Calendar
The next ESR version has been changed from 59 to 60, so we need to track changes for 6.2 here.
Alias: ltn61 → ltn62
Summary: Tracking bug for Lightning 6.1 release → Tracking bug for Lightning 6.2 release
Depends on: 1424350
Depends on: 1409560
Depends on: 719351
Depends on: 1324454
Depends on: 356002
Depends on: 321434
Depends on: 393084
Depends on: 1439182
Depends on: 758493
Depends on: 1446748
Depends on: 1444069
No longer depends on: 1448550
Depends on: 1447170
Depends on: 1451763
No longer depends on: 1447830
Depends on: 1101381
Depends on: 1406499
FYI I think we are roughly two weeks away from releasing Thunderbird version 60.
No longer depends on: 1444069
Summary: Tracking bug for Lightning 6.2 release → Tracking bug for Lightning 6.2 release (Thunderbird 60)
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/48373a3601ff
Restore Calendar printing. r=philipp
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Grrr, that patch had the wrong bug number :-(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → NEW
Depends on: 1478580
Depends on: 1479449
Depends on: 1480371
Depends on: 1481790
Any news concerning this new version? Thunderbird is update now on many platforms (60), and lightning doesn't work anymore :(
@jonathanmm: I agree it is insane, having Lightning unreleased when TB got already autoupdated on major platforms!

So far, I'm using https://ftp.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1/linux-x86_64/lightning-6.2b6.en-US.xpi with just one bug - the Google Calendar provider always asks me for new 2FA login on each startup.

@[:MakeMyDay]: I see there are still some unresolved bugs this one depends on, but none of them really seems to be a blocker for releasing "at least something". Or am I wrong?
Lightning 6.2 has been released with TB60 back in August. That it's not on ATN (fomerly AMO) is tracked in bug 1484532, which lists also possible workarounds. It is _not_ recommended to use beta version mentioned in comment 8, since it still has a lot of subsequently fixed bugs. If you need a more detailed receipe to extract Lightning from the TB pacakge, see bug 1074268.

That you seem to have no (localized) Lightning compatible to TB60 this is a packaging issue of your Linux distribution of choice, since the official packages at [1] includes a localized Lightning (since TB38). Also that you received an autoupdate is driven by your distribution - we have no control about that.

The remaining not resolved bugs were blocker candidates but didn't effectively block the release. Maybe we still can backport fixes for that once landed throughout the ESR60 life cycle.

I'm going to close this bug now since 6.2 has been released, but leave the blockers as is, since they are uplift candidates as mentioned before.

[1] https://www.thunderbird.net/
Status: NEW → RESOLVED
Closed: Last year9 months ago
Resolution: --- → FIXED
Version: unspecified → Lightning 6.2
@[:MakeMyDay] Thanks for pointing in the right direction, I haven't found that bug.
You need to log in before you can comment on or make changes to this bug.