Jira (PDB-2080) puppetdb 3.2.0 2015-10-28 Release
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2080 puppetdb 3.2.0 2015-10-28 Release Change By: Kurt Wall QA Status: Reviewed QA Risk Assessment: Low QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2080) puppetdb 3.2.0 2015-10-28 Release
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-2080 puppetdb 3.2.0 2015-10-28 Release Change By: Kenneth Barber Assignee: Wyatt Alt Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PDB-2080) puppetdb 3.2.0 2015-10-28 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2080 puppetdb 3.2.0 2015-10-28 Release Change By: Kenneth Barber Fix Version/s: PDB 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PDB-2080) puppetdb 3.2.0 2015-10-28 Release
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2080 puppetdb 3.2.0 2015-10-28 Release Change By: Ryan Senior Sprint: PuppetDB 2015-11-4 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PDB-2080) puppetdb 3.2.0 2015-10-28 Release
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2080 puppetdb 3.2.0 2015-10-28 Release Change By: Ryan Senior Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PDB-2080) puppetdb 3.2.0 2015-10-28 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2080 puppetdb 3.2.0 2015-10-28 Release Issue Type: Task Assignee: Wyatt Alt Created: 2015/10/21 9:17 AM Priority: Normal Reporter: Wyatt Alt puppetdb 3.2.0 2015-10-28 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.
