Until this point in the solent project, I have been sloopy with commits. There will sometimes be issues open, but I have been in a habit of doing change-the-world style commits.
Recently, I realised that I could start making issues not for big-picture issues, but to foreshadow and scope out a squashed commit. As an experiment, I tried it. This is working out very well. People viewing the tree, or commits should be able to get two fine things:
A succinct, correct headline in the commit history against each commit.
Ability to dig into the detail of a commit by going to my more verbose descriptions in the issue writeup.
This morning I have realised that this will benefit releases. Until now it has been adhocc. But I now have the information in front of me to produce a clear set of release notes for each release. In order to get a clean slate for this, I am doing one more "a lot of stuff has changed" style release. That is this one. (Because I do not have a clear insight into what changed since the last release before this new practice).
From 0.47 forward, we will have well-defined releases. This release marks the close of the sloppy old practices. (Thanks to Petr for his advice of six months ago. It has taken me many months to properly integrate it, but we are there now.)
Until this point in the solent project, I have been sloopy with commits. There will sometimes be issues open, but I have been in a habit of doing change-the-world style commits.
Recently, I realised that I could start making issues not for big-picture issues, but to foreshadow and scope out a squashed commit. As an experiment, I tried it. This is working out very well. People viewing the tree, or commits should be able to get two fine things:
This morning I have realised that this will benefit releases. Until now it has been adhocc. But I now have the information in front of me to produce a clear set of release notes for each release. In order to get a clean slate for this, I am doing one more "a lot of stuff has changed" style release. That is this one. (Because I do not have a clear insight into what changed since the last release before this new practice).
From 0.47 forward, we will have well-defined releases. This release marks the close of the sloppy old practices. (Thanks to Petr for his advice of six months ago. It has taken me many months to properly integrate it, but we are there now.)