Jira (PUP-9607) Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)

2019-04-11 Thread Nirupama Mantha (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha commented on  PUP-9607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
   Steps 1-6 are done. Fixed in Puppet Platform 6.0.8: https://tickets.puppetlabs.com/issues/?filter=32939   Introduced in Puppet Platform 6.0.8: https://tickets.puppetlabs.com/issues/?filter=32964  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9607) Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)

2019-04-08 Thread Nirupama Mantha (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9607  
 
 
  Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:20 PM  
 
 
Due Date: 
2019/04/10 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.0.8 and puppet-agent 6.0.8 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform