Hi folks,
Got a question about the best way to handle Forge module migrations
without screwing over anyone who uses that module.
Some time ago I started using a Puppet module from Github[1], which was
not available on the Forge at the time. I contacted the author to ask if
he would consider publishing it on the Forge and he didn't respond, so I
forked the code and published it on the Forge under my own name
(jgazeley/selinux)[2]. Since then, it has racked up quite a lot of
downloads.
This week, the original author contacted me and said his module was now
available on the Forge (jfryman/selinux)[3]. I sent a PR back to him
with my changes, and I now consider his module to be the authoritative copy.
There is no point in maintaining my fork and so I wish to remove my
module from the Forge since it will no longer receive updates. But how
can I communicate to end users who have installed my fork
jgazeley/selinux that they should migrate to use authoritative
jfryman/selinux instead? I don't want to simply delete it and have
people stuck in a dead-end release. I could publish a new version of the
module with the same code but an updated README that advises people to
migrate. Any other ideas?
Thanks,
Jonathan
[1] https://github.com/jfryman/puppet-selinux
[2] https://forge.puppetlabs.com/jgazeley/selinux
[3] https://forge.puppetlabs.com/jfryman/selinux
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/54B549B7.9000303%40bristol.ac.uk.
For more options, visit https://groups.google.com/d/optout.
