-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renewing Puppet Forge Approved Status #80
Comments
|
Please! |
|
Hello @jhoblitt , Thank you for your prompt reply. In order for this module to remain approved, the following areas need to be updated: For additional information on Puppet Forge Approved criteria please see here. Cheers! |
|
Howdy @lionce just wondering now that there's some new modern code in this repo what the status will be updated to be? I'll note for both @jhoblitt and myself, the README.md seems a bit dated now (but most info is still accurate) and we should work on updating it. I'll also note to @jhoblitt we should look into doing a release soon, ie: the whole reason I did the work on this module 💯 |
|
I'm planning to cut a new major release that drops puppet < 5 and el5 soonish. |
|
I'm currently experiencing rake target rage trying to get travis deployment to the forge up and running... |
|
w00t, looks like you figured it out? I'm just now getting back to this, looks like testing is all valid locally and I see a forge release 🎉 |
|
Yes, finally, the pdk generated |
Hey @jhoblitt,
Here at puppetlabs, we are currently going through all of our Approved modules on the Puppet Forge. We have some feedback for your module if you would be interested in retaining the approved status. If you are keen on keeping your approved status please ensure you respond as soon as you possibly can.
Many Thanks
The Puppet Approvals Committee.
The text was updated successfully, but these errors were encountered: