Closed Bug 1475839 Opened 6 years ago Closed 5 years ago

Cannot find any working lightning xpi

Categories

(Developer Documentation Graveyard :: General, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aik, Unassigned)

References

()

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

https://developer.mozilla.org/en-US/docs/Mozilla/Calendar/Calendar_Versions - here few mentioned. I could only find:
thunderbird-61.0a1.en-US.linux-x86_64.tar.bz2
thunderbird-62.0a1.en-US.linux-x86_64.tar.bz2
thunderbird-63.0a1.en-US.linux-x86_64.tar.bz2

The latest available on ftp is lightning-6.3a1.en-US.xpi , the page mentions 6.4, 6.5 but they are not available and 6.3 does not work any tb between 60 and 63.

Please fix the page. Thanks.
Hi Jorg, I know you work on Thunderbird; can you advise me on how to fix this page?

Thanks!
Flags: needinfo?(jorgk)
Hi Chris, you should direct the question to the Calendar teem, mostly Philipp and MakeMyDay. But since I'm the "jack of all trades (master of none)" around the project, I can also help you.

So let's see, people are asking for Lightning versions compatible with Daily and beta.

As we bundle Lighting with Thunderbird, you really don't need a separate XPI. If you install a Daily, you can just enable the matching XPI in the add-ons manager, or if that doesn't work, by resetting this pref:
extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103} 

The same is true for beta and even the ESR version. I'd discourage separate installation of the add-on to avoid version mismatches and malfunctions.

That said, for Daily should be able to find it here
https://ftp.mozilla.org/pub/calendar/lightning/nightly/latest-comm-central/
but it's not there.

We haven't shipped a TB 62 beta yet, so the question doesn't pose itself. For previous betas, like TB 60, the add-on is here:
https://ftp.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1/
Note: TB XX matches Lightning XX/10 + 0.2, so 60 --> 6.2.

Summarising: I'd remove the Lightning links.

BTW, 62.0b1 "Beta", https://www.mozilla.org/en-US/thunderbird/all-beta.html, redirects you to https://www.thunderbird.net/en-US/thunderbird/beta/all/ and that's TB 60, the latest beta we currently have.
Flags: needinfo?(philipp)
Flags: needinfo?(makemyday)
Flags: needinfo?(jorgk)
Building Lighting was disabled iirc since mid of TB61 cycle due to legacy extension not being working anymore, so there couldn't have been any build artefacts until last week otr so, when it returned. On top of this, TB building switched to taskcluster which I think currently doesn't generate a seperate xpi for upload anymore when doing daily/beta/release builds. Instead, Lighting is bundled with TB (and SM).

There is currently a discussion over in bug 1471326 to let taskcluster generate an xpi for the gdata provider, maybe this could be extended to also include Lightning for the convenience of the Linux distros, which traditionally built a Lightning package available in the package manager instead of letting their users make use of AMO.

Regarding the version list, which has lost its main purpose with bundling Lightning with TB and SM, I agree it should  not point people to dead links, but give a brief explanation pointing people to download TB instead. There was no beta _release_ of TB61 and Lightning 6.3.

Martin, could you update the site, so it better reflects the current situation?
Flags: needinfo?(makemyday) → needinfo?(mschroeder)
Flags: needinfo?(philipp)
I removed the outdated links and a misleading paragraph. Additional information about the new release process will be added when I got more time on my hands.
See Also: → 1499341
Flags: needinfo?(mschroeder)

Martin, everything here is done and bug can be closed?

Flags: needinfo?(mschroeder)

I think this bug can be closed.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mschroeder)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.