Posted by matijs
20/03/2020 at 13h08
Automating away your library release process because you find it boring and tedious is the worst thing you can do. People rely on your releases to be meaningful, have meaningful version numbers, and meaningful release notes. Yes, these take time. But your releases are when your users are reminded that you exist. At other times, your library is just quietly doing its thing. Releases are when your users take notice. They want to read your change log, look at the version number to see if they need to pay attention. You’re in the spotlight. This is your performance. Give your releases some love.
Tags
development, software
no comments
no trackbacks
Posted by matijs
31/12/2018 at 15h46
- Your next release should nearly always come from the
master branch.
- When updating your feature branch, prefer
git rebase master over git merge master.
- When merging your feature into
master, prefer merge bubbles over squash merges and fast-forwards.
-
bundle exec rake should run your tests.
- You still should not check in
Gemfile.lock.
- Use RuboCop. Running just
rubocop should do the right thing. If you need a specific version, add it to the Gemfile. In that case, bundle exec rubocop should do the right thing.
Tags
development, opinions, ruby
no comments
no trackbacks