search

backdrop-contrib / backdrop-drush-extension

A set of commands and boot class for Drush and Backdrop CMS.
GNU General Public License v2.0
14 stars 18 forks source link

drush rn can't tell the difference between minor & bug-fix releases #129

Open jenlampton opened 6 years ago

jenlampton commented 6 years ago

Maybe I'm not using drush rn correctly, but it seems to generate the same results, regardless of which branch I'm on, or which tag I reference.

When we do a minor version release of backdrop we need to be able to generate release notes for both the bug-fix release, and the minor version, and those two lists should be different.

If anyone has suggestions as to how those commands are supposed to be run, please let me know.

serundeputy commented 5 years ago

@quicksketch explained that this is because drush rn uses git log under the hood and git log can not give a diff log from releases that are on different branches.

closing as cant' fix.

jenlampton commented 5 years ago

But the commit message on both commits is identical, even though the commit hash is different. Drush can loop over all the commits, and if the log message is identical on two commits, it can strip one out. Drush is greater than Git here, so we should make our tools do what git cannot :)

Managing release notes for core releases is a real pain when we do a lot in the bug fix releases (which is good!) because we currently need to go through the whole commit list manually, check each issue on GitHub to see what milestone it's in, and pull out each one that was committed to a bug-fix release.

We need better tooling for this process, and Drush is already half-way there.

Today I tried crazy stuff like this:

git log --pretty=format:'* %s' --since="2018-09-16" 1.x --not 1.11.x > ~/Desktop/notes.md

... to no avail. I'm still doing it all manually :(