Opened on 02/03/2016 at 11:09:25 AM

Last modified on 12/21/2017 at 11:28:41 AM

#3623 new change

Update warning at the top of the ABP for Firefox and Chrome devbuild listings

Reported by: fhd Assignee:
Priority: Unknown Milestone:
Module: Infrastructure Keywords:
Cc: sebastian Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by philll)


Both the ABP for Firefox and the ABP for Chrome devbuild listing pages have a warning on top, however, we don't mention the fact that the standalone devbuilds don't work anymore, and that people now need to install them from AMO and the CWS respectively.

What to change

Explain the situation outlined above on the devbuild listing pages. Exact texts to be determined.

Attachments (0)

Change History (8)

comment:1 Changed on 02/03/2016 at 11:09:39 AM by fhd

  • Summary changed from Update warning at the top of the Firefox and Chrome devbuild listings to Update warning at the top of the ABP for Firefox and Chrome devbuild listings

comment:2 Changed on 02/03/2016 at 11:10:07 AM by fhd

  • Description modified (diff)

comment:3 in reply to: ↑ description Changed on 02/03/2016 at 11:52:25 AM by sebastian

Replying to fhd:

we don't mention the fact that the standalone devbuilds don't work anymore

This isn't accurate. On Chrome they still can be installed (by dragging the file into the extension management page). But they might get disabled when restarting the browser. Not sure about automatic updates either. Similarly, on Firefox AFAIK, they also still work when you disable signature checking in about:config.

So for these, who have to use older builds (i.e. testers), saying that those simply won't work would be confusing. But on the other hand, we should still make it clear to people that just want to try out the devbuild, to install the latest version from the CWS or AMO.

comment:4 Changed on 02/03/2016 at 03:30:27 PM by philll

  • Description modified (diff)

The link to older versions of ABP for Firefox dev builds at was already changed to so we should maybe think about getting rid of completely?

comment:5 Changed on 02/03/2016 at 06:15:55 PM by sebastian

It's probably not worth removing the self-hosted devbuilds (or just that page) for Firefox. In rare situations (e.g. if there is an issue with AMO) it might actually be helpful. But, except fhd or trev have more arguments, I don't mind too much.

comment:6 Changed on 02/06/2016 at 07:52:52 AM by fhd

The only thing I can think of these would still be useful is for testing older devbuilds. That did come in handy sometimes, and I don't think that's possible on AMO or the CWS. I would lean towards keeping them around for that purpose, but wouldn't mind all that much if they disappear either.

comment:7 Changed on 02/06/2016 at 10:23:29 AM by sebastian

Testing older devbuilds is something we regularly do, if it's only to test the update from an older build to the latest. However, it seems that as for AMO, you can still get older builds from there (see the link philll posted). The CWS on the other hand, doesn't let you download previous versions. So it's really only about old devbuilds for Firefox. But since we still need to host old builds for other platforms like Chrome, it probably doesn't matter whether we keep them for Firefox as well.

comment:8 Changed on 12/21/2017 at 11:28:41 AM by fhd

  • Cc trev removed

Add Comment

Modify Ticket

Change Properties
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from (none).
Next status will be 'reviewing'.
Note: See TracTickets for help on using tickets.