On 23.09.2013 16:17, William Van Hevelingen wrote:
Hi All,
ashp mentioned in #puppet that puppetlabs has not come to a decision
on doing branches per major versions yet. This email is to help start
a public discussion.
The primary use case that Im interested in is the Openstack modules
as
they rely heavily on the puppetlabs modules like apache, mysql,
rabbitmq, etc.
The 3.0 release of rabbitmq broke the openstack modules and CI
testing
for a while until bodepd pinned it to the 2.x release. This happened
a
few more times for other modules like the mysql and the apache module
so bodepd ended up pinning all the module dependencies to a major
version. I imagine some other large projects might have similar
issues
and hopefully they will respond to this thread as well.
--
Cheers,William Van Hevelingen
blkperl on irc
I can add that from my own testing the recent changes to the
puppetlabs-postgresql module have broken any module that used a version
up to the current 2.5.0 release as the current master removes the
config_hash parameter in favor of exposing the variables directly as
parameters. This broke the testing for the puppetlabs-puppetdb module
while working on my fork of it.
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-dev.
For more options, visit https://groups.google.com/groups/opt_out.
