Jira (HI-313) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Thomas Hallgren commented on HI-313 Re: Is there a JIRA ticket targeted at the release for every commit? Commits with no corresponding JIRA ticket targeted for 1.4.0: On stable: HI-273 HI-285 Additional commits on master: HI-149 HI-277 HI-303 HI-304 HI-306 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (HI-313) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Hiera / HI-313 Is there a JIRA ticket targeted at the release for every commit? Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (HI-313) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Hiera / HI-313 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:53 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log .. look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
