Puppet Dev Community Summary (2010-05-06)
Jeff McCune
Puppet Dev Community Summary
- Finished Card Total: 18 vs 17 last week
- Merged: 13 vs 11 last week
- Not Merged: 2 vs 5 last week
- Other: 3 vs 1 last week
Merged
(PR puppet/1623) (maint) Fix ENC acceptance test failure on 1.9.3 [Jeff McCune]
Merged into stable and master as 98d123f. This should be released in Puppet 3.2. This change does not affect the code, it is a minor fix of the acceptance test itself where a string was being used where an array should be used.
(PR puppet/1624) Fix various acceptance test failures on MRI 1.9.3 (maint) Fix enc_provides_node_when_storeconfigs_enabled on precise [Jeff McCune]
Merged into stable and master as abebdb0. This should be released in Puppet 3.2. These patches fix up a number of acceptance test issues with MRI 1.9.3. There are still failures that remain, but these failures are likely MRI 1.9.3-p0 specific and should not arise in more recent patch levels of 1.9.3. We have decided to not support MRI 1.9.3-p0 which also means we do not support the system Ruby installed on Ubuntu 12.04 LTS. We do, however, fully support Ubuntu 12.04 LTS with Puppet Enterprise. We'll be replacing our precise system under test with a Fedora 18 system under test in an effort to exercise the Puppet acceptance tests using 1.9.3-p327, which is supported.
(PR puppet/1619) Add the file and line number when reporting a duplicate resource [Richard Clamp]
equivalent PR merged into master in 6c34ed6 . This should be released in 3.3.0. Thanks!
(PR puppet/1629) (maint) Fix various acceptance failures on Fedora Core 18 (maint) Remove acceptance test for puppet --parseonly deprecation [Jeff McCune]
Merged into stable and master as 6cb6585. This should be released in Puppet 3.2. These patches allow the full acceptance suite to run successfully against a Fedora Core 18 system running the system MRI version 1.9.3-p392.
(PR puppet/1632) (maint) --parseonly lambda arity must match number of arguments [Jeff McCune]
Merged into stable and master as f5fb329. This should be released in Puppet 3.2. This issue was caused by the change in behavior between MRI 1.8 and 1.9 where blocks which do not have defined arguments in 1.8 will silently drop any passed arguments while MRI 1.9 will raise an ArgumentError if the number of arguments sent to the block do not match the definition of the block. This problem causedArgumentError: wrong number of arguments (1 for 0) to be displayed instead of the expected deprecation warning when executing puppet apply --parseonly or puppet master --parseonly.
(PR facter/436) Add initial functionality for exposing Rackspace Cloud data (#20468) [Jeremy Katz]
merged into master in 87c42e3. This should be released in Facter 2.0.0. Thanks!
(PR puppet/1631) (#20520) Update rgen to 0.6.2, remove Array monkey patches [Dominic Cleal]
Merged into stable and master as 9be0deb. This should be released in Puppet 3.2. Thanks again for the contribution! @domcleal Thanks for this. There had been a similar problem inside puppet itself that was worked around, but because of the changes to such a basic class. If this is breaking other systems as well, then this is definately a blocker for 3.2 so targetting stable is the right thing.
(PR puppet/1614) (#17887) Only log if message has been initialized [Dominic Cleal]
Merged into stable and master as 053a743. This should be released in Puppet 3.2. Thanks again for the contribution!
(PR puppetlabs-stdlib/150) Add a dirname function [Raphaël Pinson]
merged into master in 0c68ff6. This should be released in the next feature release of stdlib. Thanks again!
(PR armatures/40) .epp should always be the preferred extension by convention [Will Farrington]
merged by Henrik.
(PR puppet/1622) Avoid repeated lookups for "false" settings [Aman Gupta]
merged into master in c961062; this should be released in 3.3.0. Thanks again for the contribution! For reference, I added these unit testshttps://github.com/puppetlabs/puppet/commit/b922fe3f38d059ac37496879bd1f8d2e4a826106 to ensure we don't regress on this behavior.
(PR puppet/1607) Add a boolean parameter type [Dustin J. Mitchell]
merged into master in a7847c2. This should be released in 3.3.0. Thanks again for the contribution!
(PR puppet/1634) (maint) Fix enc with storedconfigs failure on Fedora 18 [Jeff McCune]
Merged into stable and master as bdb5329. This should be released in Puppet 3.2. This patch simply fixes the last remaining failing acceptance test on Fedora 18. It should provide complete (green) acceptance test coverage for Ruby 1.9.3-p392.
Not Merged
(PR puppet/1620) (maint) Handle different ssh service names in puppet resource servicetest [Nick Lewis]
Reverted a second time in bbb1ee2 due to solaris failures. We're reverting in an effort to keep work in progress to a minimum and we will circle back around to a fix as soon as possible.
(PR puppetlabs-stdlib/149) Dev/dirname function [Raphaël Pinson]
closed by contributor.
Other
Try out Luke's cross host prototype.
No comment found with summary:
(PR puppetlabs-stdlib/148) fixed a small typo in README doc [msmithgu]
Merged into master as 0aa7e94. This should be released in stdlib 4.1. Thanks again for the contribution!
Puppetcamp Austin talk
woo, Puppetcamp Austin! Talk went well, met a lot of great people, spent a lot of time in planes!
Last updated: 2013-05-06 13:51:27 -0700
Register now and take advantage of the Early Bird discount - save 25%!
Eric Sorenson
--
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 puppet-dev+...@googlegroups.com.
To post to this group, send email to puppe...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
#puppet irc: eric0
Jeff McCune
Hi Jeff, could I request one minor enhancement to this (otherwise completely awesome) report? Turns out not many people are aware that they can check the status of various pulls in flight by checking the trello board. Could you please include a link to it at the top and a little blurb like "See the team's entire state __here__" or the like? Thanks!!
Eric Sorenson
--
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 puppet-dev+...@googlegroups.com.
To post to this group, send email to puppe...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.