Interested in any articles to understand how people deploy desktop software (probably applies to mobile as well): specifically how folks cut stable releases even though there's an influx of new features/code that could create instability if you cut from master.
Would like to start from a good place from the get-go if we can. If you can, keep in mind: we're a small team that has to rapidly test our ideas too so we can't afford to build all the same tooling of a mature organization.
I found this: chromium.googlesource.com/chromium/src/+…
I've never loved feature freeze Friday but that's what we're starting to do, naturally.
I've never loved feature freeze Friday but that's what we're starting to do, naturally.
So, our approach is going to be using npm version <patch>, tagging our git repo, and shipping a client (users) / host (prod) machines weekly on that tag. We'll cut the release on Fri, test ourselves for a few days, then ship it late Monday if that all goes well.
h/t @rahulvohra
h/t @rahulvohra
