Hi All – we're trying to get on top of the backlogs of Jira tickets. Those of you who have been around for a while might remember this was the original purpose of the "Triage-A-Thon" events, when we parcelled out batches of Redmine tickets for categorization, clean-up, and prioritization. (Hi, @kartar!)
I wanted to let everyone know that this activity is going on, so if you see updates on long-dormant Jira tickets it doesn't come as a surprise. Although the commentary as we're dispositioning the tickets is boilerplate copy-pasta, these are not automatic mass-closures. Teams are going through the tickets in batches and spending some time on each one. If you get mail about a ticket that you feel is dispositioned incorrectly (such as "Cannot reproduce", when you can provide a repro case), please re-open them. Additionally, if you're interested in helping out, the query we're working through is publicly available here: https://tickets.puppetlabs.com/issues/?filter=25600# The workflow and response text for triaging tickets is available here: https://docs.puppet.com/community/puppet_projects_workflow.html#workflow-for-bugs The benefit at the end of all of this will be that we will be able to provide much better response time for new issues as they come in. Eric Sorenson - e...@puppet.com director of product, ecosystem and platform -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/B4C79B78-F85E-42E9-A0D9-5830D4640843%40puppet.com. For more options, visit https://groups.google.com/d/optout.
