610743 - Upgrading from beta5 to beta7 will show the Feedback add-on as incompatible

Status: RESOLVED WONTFIX

(Toolkit :: Add-ons Manager, defect)

Description

[Dave Townsend [:mossop]]

Ultimately caused by bug 610740 the long and short of this is that if a user upgrades from Firefox 4b5 directly to Firefox 4b7 then they will see the Feedback extension marked incompatible. Upgrading from 4b6 to 4b7 should not exhibit this issue.

I'm not sure whether we need to block b7 on this since I presume the majority of users will be upgrading from b6 however if not there are two options.

We could fix bug 610740 but obviously this means a full respin and presumably re-performing any QA around the add-ons manager.

The simpler fix would be to increase the version number for the Feedback add-on to 1.0.3.1 or something. This would require respinning builds but shouldn't have any effect on anything else so I'd expect any QA done on the builds so far to still be valid.

Comment 1

[Dave Townsend [:mossop]]

One other option would be to get a version of Test Pilot version 1.0.3 on AMO with high compatibility range. b5 users would get this compatibility update over the course of a day and once they had it upgrading to b7 would keep the updated compatibility range and keep it compatible.

Comment 2

[u279076]

FYI, discovered while running update checks for 4.0b7 on betatest channel. 
This was mostly reproducible with 4.0b5->4.0b7 updates on WinXP.

Comment 3

[LegNeato]

We won't block beta 7 on it because:

1. It doesn't happen on beta 6 -> beta 7
	** Beta5 has ~15k ADU, beta6 has ~850k

2. As in comment #1, we can put a newer version on AMO. I'll file a bug for this

3. If the extension just didn't work, we'd still get feedback (crash reports, sumo, etc) from those users and thus it'd be valuable to still get the build in their hands.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Dave, what is left to do on this bug?

Comment 5

[Dave Townsend [:mossop]]

Nothing, this really became a wontfix as we didn't block on it. We fixed the problem going forward by remembering to increase the add-on's version.