The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #11261

Update README to indicate that the puppet-module-tool is essentially dead after being merged into core puppet.

Added by Matt Robinson over 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:12/07/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-Spent time:-
Target version:-
Keywords: Affected URL:
Branch:

We've Moved!

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.


Description

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.


Related issues

Related to Puppet - Feature #7656: module tools should be a face Closed 05/24/2011 12/05/2011

History

#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?

#2 Updated by Nigel Kersten over 2 years ago

agreed. We don’t announce until we have the clear replacement publicly available, and we’ll just have to bear the cost of patches till then.

We may be able to get such folks to rebase their patches against the new Face version in the mean time?

#3 Updated by Garrett Honeycutt over 2 years ago

We need to update redmine to reflect this. Currently it points to the repo for the deprecated puppet-module-tool.

#4 Updated by James Turnbull over 2 years ago

Are there any outstanding patches? I thought most had been merged and/or Kelsey had applied stuff. Might be moot.

#5 Updated by Kelsey Hightower over 2 years ago

Everything has been merged into the 2.7.x branch as active development is currently taking place there.

#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. :–)

#8 Updated by Chad Metcalf about 2 years ago

  • Status changed from Accepted to In Topic Branch Pending Review

This looked easy enough and it also got me when I was looking to the module having ruby 1.9.2 issues so I updated the README.

https://github.com/puppetlabs/puppet-module-tool/pull/18

#9 Updated by Nick Fagerlund about 2 years ago

  • Status changed from In Topic Branch Pending Review to Closed

That pull request got merged a month ago, so this bug shouldn’t be open anymore.

#10 Updated by Daniel Pittman about 2 years ago

  • Assignee deleted (Matt Robinson)

Also available in: Atom PDF