Even though the article "Commit messages are not titles" is dated 2015 it got some traction this week on Hacker News. If you would like to see the discussion on HN you can find it here. Pretty interesting/controversial point of view by Salvatore Sanfilippo but I do agree to this. A commit message from my position must serve two purposes: explain what this commit contains and what it does. If its a title I'm fine, if not I'm fine, too. Nevertheless you should settle to a convention in your team to which everybody sticks.
A nice introduction to CloudEvents has been delivered by Doug Davis, Clemens Vasters, Klaus Deissner and Vladimir Bacvanski at KubeCon 2019. You can watch their session online. Watch CloudEvents - Intro, Deep-Dive and More! if you are interested in understanding how CloudEvents can serve purpose to you.
Always interesting how big software shops handle changes in API changes or even breaking changes in general. Shopify which is unquestionable a big software shop has published "How Shopify Manages API Versioning and Breaking Changes" which goes in detail on handling and dealing with this kind of changes.
Another great article from a big software shop comes from Amazon. If you have ever had to deal with deployments of stateful services you know this isn't as easy as it sounds in the first place. My money quote from "Ensuring rollback safety during deployments" is:
Ensuring that we can roll back a deployment without any disruption for our customers is critical in making a service reliable.
If you are interested in more articles like this you should definitely have a look at the The Amazon Builders' Library.