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

[SERVER-1677] Is the Jira tidy-up done for this release and prepared for the next one? (SERVER 2.7.2) Created: 2016/11/29  Updated: 2016/12/06  Resolved: 2016/12/06

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

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

 Description   

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

This happens on Jira - we need to clean up the current release and prepare for the next release.

  • Mark the version that's going out as "Released" in the Project Admin -> Versions panel.
  • Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)
  • Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket):
  • 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone
  • 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone


 Comments   
Comment by Justin Stoller [ 2016/12/06 ]

Waiting for the release to actually mark as released.

Not creating new version (a 2.x version exists already and we do not know if the next release will be 2.7.3 or 2.8.0).

Queries:
Fixes for SERVER 2.7.2 = https://tickets.puppetlabs.com/issues/?filter=23707
Introduced in SERVER 2.7.2 = https://tickets.puppetlabs.com/issues/?filter=23708

Generated at Fri Dec 13 09:20:37 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.