Jira (PDB-3402) Is the code ready for release? (PDB 4.4.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3402 Is the code ready for release? (PDB 4.4.0) Change By: Rob Browning Fix Version/s: PDB 4.4.0 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-3402) Is the code ready for release? (PDB 4.4.0)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3402 Is the code ready for release? (PDB 4.4.0) Change By: Rob Browning Team: Systems Engineering 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-3402) Is the code ready for release? (PDB 4.4.0)
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3402 Is the code ready for release? (PDB 4.4.0) Issue Type: Sub-task Assignee: Ryan Senior Created: 2017/04/04 8:51 AM Priority: Normal Reporter: Ryan Senior (Initial planned release date: 2017-04-04) If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%224.4.0%22
