Jira (PUP-10755) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)

2020-10-30 Thread Eric Griswold (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10755  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)   
 

  
 
 
 
 

 
Change By: 
 Eric Griswold  
 
 
Epic Link: 
 PUP-10753  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376675.1604092573000.68653.1604092620403%40Atlassian.JIRA.

Jira (PUP-10755) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)

2020-10-30 Thread Eric Griswold (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10755  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.20.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2020/10/30 2:16 PM  
 
 
Due Date: 
2021/01/13 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 (Initial planned release date: 2021-01-19) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment