This also appears to be selectively enforced. We have two different extensions with global permissions, but only one requires a 1-week review. For the other we can still push out updates in < 30 minutes.
Google Killing Chrome Extensions with 1 Week Publishing Delays
11–20 of 46 posts
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#12While you are, of course, welcome to call upon Google to improve the review speed, there are obvious things you can do on your side as well. First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. In the meantime, you can offer your users to switch to "developer mode" and install the extension manually. I personally would be against the centralized nature of Chrome extens…
Are the reviews done by humans?
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#13Earlier quoted context omitted.
For a typo? Did you read the post? If I update the text or change a typo they take a week to release the update. During this time I can't release another version of my app.
They don't know you only fixed a typo until they've had time to review it
[deleted]
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#14While you are, of course, welcome to call upon Google to improve the review speed, there are obvious things you can do on your side as well. First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. In the meantime, you can offer your users to switch to "developer mode" and install the extension manually. I personally would be against the centralized nature of Chrome extens…
> First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days.
Are you a developer? This is literally the definition of continuous delivery.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#15Given how much malware the Chrome Web Store pushes, and how sensitive of data extensions have access to, actually taking the time to properly review updates is absolutely warranted.
For a typo? Did you read the post? If I update the text or change a typo they take a week to release the update. During this time I can't release another version of my app.
Improve your QA process and you will not be waylaid by something as simple as a typo.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#16A "5 line diff" is absolutely enough code to add something malicious.
Why does it take a week to accept/deny that...? Note that they aren't actually DOING anything in this week. The Polar extension is literally just sitting waiting for someone to approve it because I updated the images.
They've got a queue to work through. I am sure the queue is prioritized in a way that is not to your advantage (i.e. most popular extensions get reviewed more quickly).
Why don't you suggest your users to switch to a browser that does not force them to use a central repository that's too slow to get your updates? You need to convince them at the same time that there are no benefits lost to the way Chrome Web Store operates.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#17While you are, of course, welcome to call upon Google to improve the review speed, there are obvious things you can do on your side as well. First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. In the meantime, you can offer your users to switch to "developer mode" and install the extension manually. I personally would be against the centralized nature of Chrome extens…
> First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days. Are you a developer? This is literally the definition of continuous delivery.
Haha, nope, it is not. CD includes testing your changes prior to delivery (it's why it's commonly referred to as CI/CD).
Btw, instead of attempting ad-hominem attacks, perhaps you should stop for a bit and reconsider why you are getting so many down-votes around here.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#18Given how much malware the Chrome Web Store pushes, and how sensitive of data extensions have access to, actually taking the time to properly review updates is absolutely warranted.
For a typo? Did you read the post? If I update the text or change a typo they take a week to release the update. During this time I can't release another version of my app.
The typo case is certainly unfortunate. This policy changes does present new challenges to product planning and associated marketing, and I sympathize with the short term impact that has on you and others similarly situated. I hope you and others are able to adapt as others who develop for centralized platforms have had to do so.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#19Given how much malware the Chrome Web Store pushes, and how sensitive of data extensions have access to, actually taking the time to properly review updates is absolutely warranted.
The week long delay could also be a reflection of how understaffed that team is. Or they haven't yet automated what can be done automatically. It doesn't necessarily mean that the code review is thorough.
Re: Google Killing Chrome Extensions with 1 Week Publishing Delays
#20A "5 line diff" is absolutely enough code to add something malicious.
Why does it take a week to accept/deny that...? Note that they aren't actually DOING anything in this week. The Polar extension is literally just sitting waiting for someone to approve it because I updated the images.
Presumably they are doing something during that week; namely code reviewing all the patches in front of yours in the queue.
Don't get me wrong. I, too, wish that other developers would drop whatever they're doing on demand to prioritize my immediate needs. I would also prefer that they waive their normal security concerns because, after all, I already know that I am trustworthy. I've got enough self awareness not to publish a blog post about it, though.