Jira (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Morgan Rhodes Sprint: Release Engineering Hopper 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.197062.1497981603000.164044.1615490884727%40Atlassian.JIRA.
Jira (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Zachary Kent Sprint: Release Engineering Hopper 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.197062.1497981603000.162729.1615408442324%40Atlassian.JIRA.
Jira (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Zachary Kent Sprint: 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.197062.1497981603000.162685.1615408382203%40Atlassian.JIRA.
Jira (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Kenn Hussey Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Russell Mull Fix Version/s: PDB 5.0.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Kenn Hussey commented on PDB-3568 Re: PuppetDB 5.0.0 2017-06-27 Release Rob Browning can this be resolved now? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Change By: Rob Browning Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3568) PuppetDB 5.0.0 2017-06-27 Release
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3568 PuppetDB 5.0.0 2017-06-27 Release Issue Type: Task Assignee: Rob Browning Created: 2017/06/20 11:00 AM Priority: Normal Reporter: Rob Browning PuppetDB 5.0.0 2017-06-27 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
