Commerce Guys maintains a suite of ecosystem modules that give merchants easy access to third-party integrations as part of leading the Drupal Commerce project.
Historically, the issue queues for these modules were looked at when a client requested it or someone from our team had spare time, but that timing was pretty irregular. To provide developers and merchants with a better experience, we’ve decided that moving forward we’re committing dedicated time to review these third-party issue queues on a regular basis.
Once a week, we’re setting aside time to review new issues in the queues. We’ll use that time to do several things: identify bugs, direct people toward resources to help them solve their problems more quickly, identify earlier when we need more information from the reporter, and help move community patches forward.
Cleaning the Current Queues
As part of this renewed focus on integrations, we’re starting by cleaning up the issue queues. To give ourselves a clean slate, we’ll be closing a lot of these older issues. This will allow us and other contributors to focus on relevant problems. There are a significant number of old issues hanging around that represent duplicate bug reports, tasks that were resolved via other patches, or issues that cannot be resolved without clear steps to reproduce the problem.
What to if we close an issue you still need resolved?
If we close an issue that you’re still having problems with please let us know! For old support requests, we likely closed them because the issue queue isn't the best place to get Commerce support. To find a broad base of people who are willing and able to help you (including us), please use the Drupal Answers Q&A forum with the drupal-commerce tag instead.
For old bugs, the best thing to do would be to reopen the issue with additional information. Please include any error messages you’re seeing, custom code that may affect the module, and clear steps to reproduce the bug. Screenshots or recordings of the issue in action would be great, too!