Jira (PUP-4721) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-4721 Is there a commit for every JIRA ticket targeted at the release? Change By: Joshua Cooper Assignee: KyloGinsberg JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PUP-4721) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Josh Cooper commented on PUP-4721 Re: Is there a commit for every JIRA ticket targeted at the release? COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF PUP 4.2.0) PUP-4703 RE-4831 ALL ISSUES WERE FOUND IN GIT Kylo Ginsberg already mentioned ~ PUP-4703 ~ above. RE-4831 was a change to 3.x to bundle openssl 1.0.0.s on windows, and can be ignored because a corresponding change was made in https://github.com/puppetlabs/puppet-agent/commit/5cb721a82476e12158072055c5caddc5cb548100 for puppet 4.x (puppet-agent 1.2.x) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4721) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg commented on PUP-4721 Re: Is there a commit for every JIRA ticket targeted at the release? I did a rough draft of the two-way (git - jira) reconciliation and corresponding jira scrub as of 6/14: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF PUP 4.2.0) PUP-4573 PUP-4703 UNRESOLVED ISSUES NOT FOUND IN GIT PUP-3088 Ready for Merge UNRESOLVED ISSUES FOUND IN GIT PUP-4386 Ready for Test PUP-4698 Ready for Test PUP-4747 Ready for Test PUP-4573 and PUP-4703 can both be ignored as they are both 3.x changes merged up to
Jira (PUP-4721) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4721 Is there a commit for every JIRA ticket targeted at the release? Change By: Kurt Wall QA Risk Assessment: Low QA Risk Assessment Reason: N/Aforreleasetickets QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PUP-4721) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4721 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/06/09 3:19 PM Priority: Normal Reporter: Kylo Ginsberg 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 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. Add Comment
