Jira (HI-243) Is there a commit for every JIRA ticket targeted at the release?

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Is there a commit for every JIRA ticket targeted at the release? the log of commits between 1.3.2 and stable head is: 7b4819f (packaging) Add Trusty cow to stable branch 37bb93b (#22142) Extract method to list all hierarchy files 505ae05 (#22142) Substantial speed increase in lookups e11d425 (HI-236) Raring went EOL in Jan 2014, so we should no longer build packages for it. b196dbe (HI-232) Hiera should replace ruby-hiera 7752c8a (maint) Pin rake for acceptance to the last 1.8 compatible version 7769914 (maint) Pin rake to the last 1.8 compatible version fa12083 (hi-149)(packaging) Remove Fedora 18 from the default package builds #22142 is HI-239 , and the 7b4819f is HI-185 (or so I think; "adding trusty" which is also on master) Add Comment   Hiera / HI-243 Is there a commit for every JIRA ticket targeted at the release? Ensure all tickets targeted at the release have a corresponding commit   * git log <old tag>..<new tag>   * This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers   * [ticketmatch.rb script|https://gist.github.com/hlindberg/9520023] is a ruby script that helps with "Is ther... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.