People write comments like this one because it's useful to know the published release in which the issue is fixed.
Not sure how many developers missing this information, but I certainly do.
Is that something that can be done in automatic way? Or it can only be a property on issue?

CommentFileSizeAuthor
#3 tags.png39.83 KBLeksat
released-in.png143.62 KBLeksat
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Leksat created an issue. See original summary.

drumm’s picture

Project: Drupal.org infrastructure » Project issue tracking
Version: » 7.x-2.x-dev
Component: Other » Issues

Issues are already complicated enough, I'd want this to be automatic only. The tricky part is having a good algorithm for it. For example, some issues have bits of fixes that arrive in multiple versions.

Might want to move this to versioncontrol_project's issue queue if we depend on commit messages.

Leksat’s picture

FileSize
39.83 KB

What about the following?

If we add output of "git tag --contains={hash}" to commit messages?

Maybe not all tags, but just the first one. Or first ones from each branch. Anything would be helpful.