The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Update README to indicate that the puppet-module-tool is essentially dead after being merged into core puppet.
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
Now that the puppet module tool has been merged into core puppet as a face, the git repo needs to be clear that we won’t be developing the standalone tool further.
#1 Updated by Matt Robinson over 2 years ago
Nick, Nigel and or Mike, I’m having trouble coming up with a good way to word the statement that the puppet-module-tool is no longer going to be updated and is effectively dead. I think it will be easier to do once there’s a released version of Puppet with the module tool out there, so maybe I shouldn’t update the module-tool repo README until we do a puppet release. Until then we’ll just have to take any patches we receive against the module-tool and manually port them to puppet – which there shouldn’t be many of, but Dominic Cleal made a patch a couple days ago.
Thoughts and opinions?
#6 Updated by Matt Robinson over 2 years ago
There are no outstanding patches against the PMT, but there was one recently that I merged in and made sure was in the ported work. Doubt we’ll get many more between now and the next release of Puppet, but if we do, we’ll need to manually port the patch to Puppet.
#7 Updated by Dominic Cleal over 2 years ago
Agreed with Matt’s original description, it’d be a good idea to put a notice in the git README at least so the future direction of development is clear. The sort of people who pull PMT from git can also pull a dev version of Puppet.
I’d just started looking at the Forge/PMT that day, and only read out about the imminent mainline merge on puppet-dev after spending some time with it. :–)