Jira (FACT-1207) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-1207 Is there a JIRA ticket targeted at the release for every commit? Change By: Michael Smith Assignee: Kylo Ginsberg Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (FACT-1207) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Michael Smith commented on FACT-1207 Re: Is there a JIRA ticket targeted at the release for every commit? Exceptions: FACT- was committed to master, cherry-picked up to stable, then merged up to stable. So it appeared in Facter 3.0.2, and a different commit appears in Facter 3.1.0 but contains no changes. HACK and RE-3434 were merged before rewording by mistake. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (FACT-1207) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title John Duarte updated an issue Facter / FACT-1207 Is there a JIRA ticket targeted at the release for every commit? Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (FACT-1207) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1207 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/02 10:28 AM 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.
