I’m the maintainer of the linux-entra-sso webextension [1], which we provide on Chrome(ium), Firefox and Thunderbird (for almost 2 years now). Previously we self-distributed the extension, which worked quite well. However, our users asked to also get a listed version. This brings some challenges, making us consider going back to self-distribution:
we release in a cadence of ~ once per month regular (bugfixes more quickly)
we release all versions together to have a common feature set across platforms
If the review times are longer than our release cadence, we can’t ship any Firefox versions - simply because the review re-starts on the next update. We just ran into exactly this issue after 11 days of waiting. Also, we can’t ship bugfix releases in a timely manner. If the review time is just a couple of days, that’s fine.
When several versions are waiting, the reviewer always reviews the latest one, so shipping a new version doesn’t leave the Firefox release stuck behind an older pending version.
That said, I’m sorry I can’t promise specific review times. We have been seeing a large influx of new submissions, which has stretched the queue. We wrote about what is happening and what we are doing about it here: Important update: Addressing the long manual review times ( Important update: Addressing the long manual review times ).
In the last review, the reviewer raised some issues. Have you addressed those in the new version?
Thanks for the clarification. Still I’m wondering if a new version means keeping the position in the review queue or dropping the old one and inserting the new one at the back? This makes a huge difference, as it still means I’m just re-injecting the new version into the queue but nothing is ever reviewed.
Regarding the last review that rejected our extension (Version 0.6 from June 20, 2024):
Back then we have been rejected, because the AMO policy was different and we fell under the “closed user group” (which is debatable, but we accepted it). Since then, the policy has changed to explicitly allow “closed user groups” on public listings on AMO [1] .
TL;DR: our extension did not change much since then, but the policy on AMO changed which now allows us to be listed.
A new submission doesn’t drop your spot in the queue. However, it’s preferable not to submit versions that will radically change the source code compared to the previous version.
That way, you are making the life of reviewers easier and the review process much quicker!
In terms of Version 0.6, I totally didn’t see the 2024
