Jira (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Henrik Lindberg commented on PUP-5407 Re: puppet 3.8.4 2015-11-02 Release Fixed in PUP 3.8.4 https://tickets.puppetlabs.com/issues/?filter=15901 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 (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Henrik Lindberg commented on PUP-5407 Re: puppet 3.8.4 2015-11-02 Release Introduced in PUP 3.8.4 https://tickets.puppetlabs.com/issues/?filter=15900 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 (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Note that this date is a bit of a placeholder, but I wanted to get this ticket ready now.The code itself is ready so, the scheduling is mostly a question for [~melissa] and [~jorie]. Ideally we'd do this sometime before 11/11. puppet 3.8.4 2015-11-02 ReleaseWhen 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. 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
Jira (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg 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 (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Sprint: Language 2015-11-11 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 (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Change By: Kylo Ginsberg Scrum Team: Language 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 (PUP-5407) puppet 3.8.4 2015-11-02 Release
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5407 puppet 3.8.4 2015-11-02 Release Issue Type: Task Assignee: Henrik Lindberg Created: 2015/10/22 10:51 PM Priority: Normal Reporter: Kylo Ginsberg puppet 3.8.4 2015-11-02 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.
