Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hi,
would it be possible to show the latest git commit messages on the form to create a new project release?
I am usually lost when I have to type the release notes..
Maybe this can result in better release notes all over the place :)
Comments
Comment #1
juliangb CreditAttribution: juliangb commentedThis is not a project application...
Comment #2
donquixote CreditAttribution: donquixote commentedI did not even know this other category does exist.. (and did not see it in a list)
Comment #3
marvil07 CreditAttribution: marvil07 commentedActually, Git Release notes can solve your problem, it's a drush extension that help there ;-)
Comment #4
donquixote CreditAttribution: donquixote commentedNice. I hope this does work outside of a Drupal install?
http://drupal.org/project/grn
Comment #5
donquixote CreditAttribution: donquixote commentedYes it does. This is cool.
----------
On the other hand, it is just a commandline output, where I would prefer to have this integrated in the web UI where you type the release notes.
So, what about we (or someone)
- Install grn on drupal.org
- Whenever a node/add/project-release form is to be shown, we run the drush command (or something equivalent) to prefill the summary field.
- Alternatively, have a js button to pre-fill the field.
I imagine that not just I will benefit from this, and in general we will get more meaningful release notes.
Comment #6
Josh The Geek CreditAttribution: Josh The Geek commentedComment #7
dwwI disagree with the assertion that making it easier to cut and paste a river of commit messages into the release nodes will lead towards: "in general we will get more meaningful release notes". In fact, I suspect the opposite will be true.
Release notes should be the curated list of changes that humans actually care about when deciding if it's time to upgrade. If you want to see all the commit messages, use the revision control system and see for yourself. Years ago, I wrote the predecessor of grn, the one that talked to CVS, and the result was bazillions of release nodes with way to much noise and almost no signal. End users almost never read release notes, since they can't make sense of all the commits and developer-speak in them.
If you use grn, use it only as a starting point. Edit it down to only include the changes end users actually need to hear about. Re-word the messages so that mere mortals can understand them. Etc. ;)
Anyway, I don't see this as worth fixing on d.o. grn exists for those who want to use it. I'd rather see this effort going into a 1000 other fixes and improvements that all need to happen and would have much more tangible benefits.
Thanks,
-Derek
Comment #8
donquixote CreditAttribution: donquixote commentedFair point.