Jira (HI-454) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Josh Cooper commented on HI-454 Re: Is the Jira tidy-up done for this release and prepared for the next one? Marked HI 3.0.3 as released Created HI 3.0.4 Introduced in HI 3.0.3: https://tickets.puppetlabs.com/issues/?filter=15428 Fixes for HI 3.0.4: https://tickets.puppetlabs.com/issues/?filter=15430 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 (HI-454) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title John Duarte updated an issue Hiera / HI-454 Is the Jira tidy-up done for this release and prepared for the next one? Change By: John Duarte QA Status: Reviewed 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 (HI-454) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Hiera / HI-454 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/02 10:51 AM Priority: Normal Reporter: Kylo Ginsberg 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
