Extension Review Best Practises - Webpack

[Tim Dykes]

G'day guys - looking for some best practises in making the review process as smooth as possible.

I currently have an extension thats been active for 10+ years, I publish a 'production' version and a 'early access' version of the one extension. Both versions are automatically publish out via CI/DI workflows from a single repo and ultimately have the same features. Early access is published weekly and has a few more debug flags setup via its webpack. Production goes out monthly and has slightly more minimisation setup.

I'm seeing Production reviewed and released via the chrome store within a few hours, Production is taking 3-4 days for review/approval each time. Given they have the same code/features/details in their store listing I'm wondering if something in my webpack is making one harder to review than the other or if there is some other factor at play that I can change to make the process smoother.

[Oliver Dunk]

Hi Tim,

Could you share your extension IDs? I'd be happy to take a quick look.

That said, my advice is usually to avoid over indexing on review times and trying to make any specific changes. There are so many factors that can influence review time and many of these are out of your control, so it could be that you spend a significant amount of time making changes to the package you submit and don't see any difference. I know that isn't the most actionable advice, but I also want to be honest.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/4877b76a-c6fa-441b-95ba-c0f87907a105n%40chromium.org.