Jira (PUP-3211) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3211 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Andy Parker Assignee: HaileeKenney AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3211) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Andy Parker assigned an issue to Hailee Kenney Puppet / PUP-3211 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Andy Parker Assignee: AndyParker HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-3211) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Andy Parker created an issue Puppet / PUP-3211 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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.Y', Save as Introduced in X.Y.Y, 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
