On 2014-16-06 19:40, Andy Parker wrote:

Week of June 8th, 2014

** Next PR Triage Wednesday, June 18th @ 10:00 am Pacific. **

Priorities


   1. Puppet 3.7.0/4.0.0 with the final language polish as well as many
other changes.
   2. Windows stability improvements
   3. CFacter on the march

Commentary

PUP-514 has landed! This is a major new feature for the puppet language.
You can now specify types on the arguments to classes, defines, lambdas,
and EPPs. The type system has been around for a little while now, but
until recently wasn't the kind of thing that most people used. Now it is
tied much more directly into the language in a way that should let you
get rid of a lot of the validate_x() function calls and provide
classes/defines that clearly specify what the allowed values are for
parameters.

This is a huge new feature. Henrik has been thinking through the type
system for a while now and slowly evolving it in the background. You can
see his writings on the topic at
http://puppet-on-the-edge.blogspot.com/2014/02/puppet-internals-puppet-type-system.html.
Since this is such a big feature, and so important to the correctness of
any manifests that use it, I'd like to ask for some help. Please grab
the master branch up puppet and try out converting your manifests to
using the types. See what you can express with them, see what you can't.
If it behaves in ways that are unintuitive, hard to understand, out
write wrong or self-contridictory, please let us know!

I am working on a blog post to cover the new type checking features and the various ways they can be used - either "automatically" by declaring parameters as typed, or by using the assert_type function when the declarative approach is not enough. (Hope to have the blog post ready in a day or so) - it will appear as part of the type system blog posts - i.e. indexed from this page: http://puppet-on-the-edge.blogspot.se/2014/02/the-puppet-type-system-blog-posts.html).


The work to convert to using FFI for windows is nearly complete. The
build out to getting x64 support is continuing (it requires using ruby 2.0).
CFacter should hit 0.1.0 this week and Facter should get a 2.1 release.


Data


Since we are aiming for the 3.7 release, I'm going to start publishing
the version burn-up. It gives an indication about how we are tracking to
finishing the known work to a particular date. However, it doesn't do a
good job of telling us how we are doing with unknown scope. A lot of the
scope growth appears to happen on Wednesdays, which would correspond
with our planning and with our PR triage where we pull in tickets.

Inline image 1

http://pullrequestmetrics.herokuapp.com/

Inline image 2
Inline image 3
--
Andrew Parker
[email protected] <mailto:[email protected]>
Freenode: zaphod42
Twitter: @aparker42
Software Developer

*Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September
22-24 in San Francisco*
/Register by May 30th to take advantage of the Early Adopter discount
<http://links.puppetlabs.com/puppetconf-early-adopter> //—//save $349!/

--
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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/CANhgQXswXMkp2fbHr9AF5KYdHsRWsHnCK-mext5yVE7ttEWcXQ%40mail.gmail.com
<https://groups.google.com/d/msgid/puppet-dev/CANhgQXswXMkp2fbHr9AF5KYdHsRWsHnCK-mext5yVE7ttEWcXQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.


--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/lnqr0h%249d6%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to