puppetserver 2.7.2 2016-12-06 Release (SERVER-1672)

[SERVER-1673] Is the code ready for release? (SERVER 2.7.2) Created: 2016/11/29  Updated: 2016/12/05  Resolved: 2016/12/05

Status: Resolved
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Normal
Reporter: Jeremy Barlow Assignee: Justin Stoller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: NG 2016-12-14
QA Risk Assessment: Needs Assessment


(Initial planned release date: 2016-12-06)

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.


Comment by Justin Stoller [ 2016/11/30 ]

We need acceptance tests across all of our platforms. The change for this release includes an RPM dependency change and a change to service scripts on the newest Debs.

Comment by Justin Stoller [ 2016/12/05 ]

There is no necessary agent bump and everything has passed CI as of https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppetserver_integration-system_no-conditional_smoke-stable/66/

Generated at Sun Jul 12 23:22:31 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.