3 ms·
> 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
by burtonator 8y ago
> 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.
- necovek 8y agoHaha, 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.
- chris_mc 8y agoI already don't like how you constantly push your product on HN, but now you're acting like an entitled asshole to boot. Maybe chill out and don't attack possible users?
- pwinnski 8y agoPreviously-possible users, maybe. After this, I'm guessing uptake from here is lower.
- derekp7 8y agoWould it be appropriate to re-architecture your extension, so that only the minimal code necessary is in the actual extension? And put the rest into a progressive web app? The way I think of extensions is similar to a device driver for an OS, a way to add functionality that an app needs that isn't already provided by the base platform. This way, you only need to push a new extension update whenever you need new api-level functionality, and you have total control over the rest of the user experience (regular HTML/CSS/javascript). Or would this cause the extension to be rejected by Google, on the grounds that the "api" that it adds would be too open to abuse?
- vec 8y ago"continuous delivery" != "test in production" But even if it were, why do you think continuous delivery is the appropriate choice of workflow when you don't actually control the "delivery" part?