Jira (PDB-3573) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)

2021-03-11 Thread Morgan Rhodes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Morgan Rhodes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3573  
 
 
  Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)   
 

  
 
 
 
 

 
Change By: 
 Morgan Rhodes  
 
 
Sprint: 
 Release Engineering Hopper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.197067.1497981623000.163897.1615490820807%40Atlassian.JIRA.


Jira (PDB-3573) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)

2017-06-27 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3573 
 
 
 
  Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Fix Version/s:
 
 PDB 5.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3573) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)

2017-06-27 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3573 
 
 
 
  Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3573) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)

2017-06-20 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3573 
 
 
 
  Is the Jira tidy-up done for this release and prepared for the next one? (PDB 5.0.0)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 

Created:
 

 2017/06/20 11:00 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
(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