-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi
>> I'd avoid any version of puppet that ends in a "0" like the plague if you >> want stability. > > > The project has been steadily improving in this regard, but it's definitely > been a problem. > > I have great hopes for 2.7.0 though, and the more people that test out our > RCs (hint! hint!) the better it's going to be. Awesome would be some kind of script with which I could test the new release. Something with puppet cucumber, that people could run and that would simply try to compile all the catalogs for their hosts and maybe also comparing the catalogs to the ones of the currently installed version. Also it could record compile time etc. so we wouldn't fall into another regression as we did with 2.6.0 I know more or less how I could do that with puppet-cucumber and R.I.'s catalog-diff but I lack a bit the time to setup that. But I would certainly download a tarball and run the script that I only need to point to my puppet.conf and send the feedback on that. I think this could be in general useful for future releases. Yeah I know, I'm just throwing in ideas that don't contain actual code... Sorry. ~pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3f0GsACgkQbwltcAfKi3/bNACeOw2bAr+oYL3VGoWZSLJWCpni bl4AoIx0j7pTlabE4jAkGUEX8hpbxOv0 =2EUf -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
