Jira (FACT-1029) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg commented on FACT-1029 Re: Is there a commit for every JIRA ticket targeted at the release? Final reconcile: So leaving out CFACT and RE commits, the unreconciled tickets (as of 6/14) are: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF FACT 3.0.0) FACT-976 UNRESOLVED ISSUES NOT FOUND IN GIT FACT-1011 In Progress FACT-976 is internal for now (so the script can't see it) but is in jira. FACT-1011 is the ticket tracking docs changes, so not represented in git. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-1029) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg commented on FACT-1029 Re: Is there a commit for every JIRA ticket targeted at the release? I just did a rough draft of this using ticketmatch.rb and scrubbed some tickets accordingly. Note that a ton of CFACT tickets show up as commits in git but not in the FACT project. That makes sense because we intentionally moved only open/facter-3 tickets from CFACT when we stopped tracking the work under CFACT. So leaving out CFACT and RE commits, the unreconciled tickets (as of 6/14) are: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF FACT 3.0.0) FACT-976 UNRESOLVED ISSUES NOT FOUND IN GIT FACT-1011 In Progress FACT-1044 Ready for Engineering UNRESOLVED ISSUES FOUND IN GIT FACT-1042 Ready for Test FACT-976 is internal for now (so the script can't see it) but is in jira. The other 3 are correctly in progress. We should do a final pass of ticketmatch once those issues are in.
Jira (FACT-1029) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kurt Wall updated an issue Facter / FACT-1029 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 (FACT-1029) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1029 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/06/09 3:29 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
