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

2015-07-21 Thread Kylo Ginsberg (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Is there a JIRA ticket targeted at the release for every commit?  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF PUP 4.2.1) 
 
 
 
 
PDOC-16 
 
 
 
 
PUP-4848 
 
 
 
 
RE-5087 
 
 
 
 
ALL ISSUES WERE FOUND IN GIT
 
 
 
 
 
 
 
Re those three: 
 



PDOC-16
 was moved to 

PUP-4910

 



PUP-4848
 was a 3.8 fix which was merged up to 4.x but is a no-op in 4.2.1 (zero code change)
 

RE-5087 was a SLES 10 packaging change (PE platform)

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

2015-07-08 Thread Kylo Ginsberg (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4831 
 
 
 
  Is there a JIRA ticket targeted at the release for every commit?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Created:
 

 2015/07/08 8:54 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.