Puppetlabs Modules Now Have Tiered Review Cycles

If you've been watching the  or check out the next Puppet Modules Roundup post for a summary! 

On the Issues With CI for community PRs 

We're aware that testing community contributions has been harder than it should be. The current pull request model makes it difficult to run the full acceptance test suite against a contributor's PR without manual effort by Perforce employees, which slows reviews and discourages contributions. Solving this is a priority for the team and we have been prototyping an improved approach that will meet both user expectations and maintaining a secure infrastructure. We’ll share specifics once it's working end-to-end. This is a known gap we're committed to closing. 

How We'll Show Our Work 

• Monthly Modules Roundup. We publish a roundup each month covering what  modules have been released, who contributed, and what’s next. You can follow the series here: Puppetlabs Modules Roundup on dev.to. 


• Contributor recognition. The release notes on the Forge and in the monthly roundup will call out merged community PRs by name. 


• Public GitHub transparency. We will be following up with contributors directly in pull requests and issues in our open source modules. In advance of a release, we will continue to merge and close PRs so that you can see what will be included in an upcoming release. 

How can you help? 

Keep contributing! Keep filing issues. Keep telling us when a module is in your way. If a PR of yours has stalled out, please rebase it or comment on the PR. And if the tiering above looks wrong for how you use Puppet day-to-day, let us know! The whole point of publishing this article is so that the community can understand what is changing and also to invite you to shape where the priority goes. 

Tiering is not a one-way decision.  

The tiers outlined here have been based on the activity we have observed in our analytics and the importance identified by customers. If a module you depend on isn't in the tier you think it should be, or perhaps a long-waiting PR or issue is blocking you, reach out via the Puppet Community Slack or leave a comment on the monthly Puppet Modules Roundup posts. We want your input to make sure the tiering meet the needs of all our users.