3 ms·
A couple of practical solutions here. 1) Automate your releases and run that on a CI server if you can. "It works on my laptop" is not ideal for releasing stuf
by jillesvangurp 7y ago
A couple of practical solutions here.
1) Automate your releases and run that on a CI server if you can. "It works on my laptop" is not ideal for releasing stuff.
2) Have a release branch, and only allow stuff to be merged that passes your CI tests and trigger the automation under step 1 after a merge to your release branch. This works for continuous deployment but can also work for releases of other stuff. If you use semantic versioning, the CI server should tag the release and publish the artifacts. That's one less thing that can go wrong. If you forgot to bump the version number on your master branch, the build should fail.
3) Have a release checklist. People forget stuff and having a small list of "Are the release notes and readme updated? Is our CI not complaining? Have all PRs been merged? Etc. Even with the above, premature releases through an early merge to your release branch could happen. A checklist can prevent that. And of course, if you can integrate those checklists into your CI. If your release notes are unchanged since the last version
4) Release often. Small deltas are less work to test and less risky to impose on users and you get feedback on stuff you did earlier.