PuppetDB 5.0.0 2017-06-27 Release (PDB-3568)

[PDB-3573] Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0) Created: 2017/06/20  Updated: 2017/06/27  Resolved: 2017/06/27

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 5.0.0

Type: Sub-task Priority: Normal
Reporter: Rob Browning Assignee: Rob Browning
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Sprint: Hopper/Triage
Release Notes: Not Needed
QA Risk Assessment: Needs Assessment

 Description   

(Initial planned release date: 2017-06-27)

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

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