Jira (PUP-5364) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5364 Is the code ready for release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/10/14 8:40 AM Priority: Normal Reporter: Kylo Ginsberg 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%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%221.2.7%22
Jira (PUP-5364) Is the code ready for release?
Title: Message Title Josh Cooper commented on PUP-5364 Re: Is the code ready for release? Waiting to hear about QENG tickets relating to jenkins job configs 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-5364) Is the code ready for release?
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5364 Is the code ready for release? Change By: Josh Cooper Assignee: Kylo Ginsberg Josh Cooper 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-5364) Is the code ready for release?
Title: Message Title Josh Cooper commented on PUP-5364 Re: Is the code ready for release? QENG tickets were deferred to 1.3.0. Now waiting on AIX validation. 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-5364) Is the code ready for release?
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5364
Is the code ready for release?
Change By:
William Hopper
If there are any 1) Check that the version dependencies expressed number in source for each component is correct for the code base, make sure these are up to date current release . For Puppet, make sure This should have been done as the shas used to build last step of the MSI are correct previous release . For * Puppet -Server, make sure all references to the : check `lib/ puppet / version .rb` for the PUPPETVERSION variable. * Facter: check `lib/CMakeLists.txt` for the LIBFACTER_VERSION variables, and ensure the major, minor and patch settings are correct. * Hiera: check `lib/hiera/version.rb` for the VERSION variable. All tests (spec, acceptance * Mcollective: check `lib/mcollective.rb` for the VERSION variable. * Pxp-agent: check `CMakeLists.txt` for the APPLICATION_VERSION_STRING variable.2 ) should be passing on all platforms Check that each component config in the puppet-agent repo points to the correct SHA for both stable & master the release . * The configs are in `configs/components/*.json`. * If a new platform has been added, make sure Ensure that platform has acceptance testing for each component , new features have decent coverage, etc any changes between the listed ref and the head of stable are known and captured in this ticket . etc Ensure your stable branch is up to date and use {{git log --pretty=oneline . .stable}} to view additional commits. * If Ensure that the release is going to be cut from a sha {{windows_puppet.json}} and {{windows_ruby.json}} configs point at the correct tags. Generally , rather than the head Windows team will have created these tags ahead of a branch time , make sure but this step may require tagging the respective Windows repos if not.3) Once the component configs in puppet-agent are verified to be correct, ensure that sha specifically every component has successfully gone through spec CI. * First, check https: / acceptance / etc jenkins . puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet%20Agent%20Daily/ to ensure that the AIO daily job has completed successfully, and that all tests are passing. * Move all items Next, check http://kahless.delivery.puppetlabs.net/view/pxp-agent/ to ensure that should be moved from Ready for pxp-agent has passed all tests in CI to Ready for Review . Have 4) Ensure that all tickets been targeted at this release for all components are resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board . * Use the following filter to view all tickets for all components for this release: https://tickets.puppetlabs.com/issues/?jql= project fixVersion % 20in% 20 ( % 3D 22puppet-agent % 20PUP 201.2.7 % 20AND 22 % 20resolution 2C %20% 3D 22PUP % 20Unresolved 204.2.3 % 20AND 22 % 20fixVersion 2C %20% 3D 22FACT % 203.1.1%22%2C% 20% 221 22HI%203 . 2 0 . 7 4 %22 ) * Any tickets which are not resolved should be brought to the attention of the appropriate scrum team so they can be resolved for the release.
Jira (PUP-5364) Is the code ready for release?
Title: Message Title William Hopper commented on PUP-5364 Re: Is the code ready for release? (whoops - am playing around with Jira formatting while revamping these tickets - disregard updates ) 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-5364) Is the code ready for release?
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5364
Is the code ready for release?
Change By:
William Hopper
1) Check that the version number in source for each component is correct for the current release. This should have been done as the last step of the previous release. * Puppet: check ` {{ lib/puppet/version.rb ` }} for the {{ PUPPETVERSION }} variable. * Facter: check ` {{ lib/CMakeLists.txt ` }} for the {{ LIBFACTER_VERSION }} variables, and ensure the major, minor and patch settings are correct. * Hiera: check ` {{ lib/hiera/version.rb ` }} for the {{ VERSION }} variable. * Mcollective: check ` {{ lib/mcollective.rb ` }} for the {{ VERSION }} variable. * Pxp-agent: check ` {{ CMakeLists.txt ` }} for the APPLICATION_VERSION_STRING variable.2) Check that each component config in the puppet-agent repo points to the correct SHA for the release. * The configs are in ` {{ configs/components/*.json ` }} . * Ensure that for each component, any changes between the listed ref and the head of stable are known and captured in this ticket. Ensure your stable branch is up to date and use {{git log --pretty=oneline ..stable}} to view additional commits. * Ensure that the {{windows_puppet.json}} and {{windows_ruby.json}} configs point at the correct tags. Generally, the Windows team will have created these tags ahead of time, but this step may require tagging the respective Windows repos if not.3) Once the component configs in puppet-agent are verified to be correct, ensure that every component has successfully gone through CI. * First, check https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet%20Agent%20Daily/ to ensure that the AIO daily job has completed successfully, and that all tests are passing. * Next, check http://kahless.delivery.puppetlabs.net/view/pxp-agent/ to ensure that pxp-agent has passed all tests in CI.4) Ensure that all tickets targeted at this release for all components are resolved. * Use the following filter to view all tickets for all components for this release: https://tickets.puppetlabs.com/issues/?jql=fixVersion%20in%20(%22puppet-agent%201.2.7%22%2C%20%22PUP%204.2.3%22%2C%20%22FACT%203.1.1%22%2C%20%22HI%203.0.4%22) * Any tickets which are not resolved should be brought to the attention of the appropriate scrum team so they can be resolved for the release.
Add Comment
