What happens when your process misses something? Things don't happen. I
forgot to put a reminder in our work items last week to send this email,
and so....it didn't get sent :( Sorry about that.

Last week we spent on finalizing much of the 3.2 release. There was some
back and forth about supporting the module tool on windows, and that has
continued into this week. We also fixed #18211 and #14766, so splay and
runinterval should work in 3.2. We also fixed a mis-feature that had crept
in from our support of webrick and ruby 1.9.3 in which the master started
doing reverse DNS lookups for every request to it. Documentation for the
new future parser got some love and an example module was put together to
show what can be done with the new syntax. In slightly less user centered
news, we also swapped around how we were going to deal with dependencies on
libraries, which caused a cleanup of our Jenkins CI jobs to start using
bundler.

So what is up this week?

  * Windows support for the module tool
  * Cut a 3.2 RC
  * Work toward testing the packages we produce in our test infrastructure

The last few releases the team has downed tools during the RC period to do
exploratory testing. We've manually tested the packages we produce, setups
of puppet across different systems, the features we had been working on,
etc. The main point of that was to make sure that we spotted any problems
in the RC and a secondary part was to make sure that we didn't move on
before the release was final so that if any problems come up we were able
to react.

We actually do testing like that throughout the cycle, but the part that is
relegated all the way to the end is actually trying out the packages.
Testing them all out is also the most painful part. So instead of doing our
exploratory testing this time, we are instead taking the time to update our
testing and build pipeline to start testing from these artifacts that we
actually ship. This investment into our ability to ship should make us able
to ship higher quality with less effort in the future.

-- 
Andrew Parker
[email protected]
Freenode: zaphod42
Twitter: @aparker42
Software Developer

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**The first 150 tickets sold will be available at a 35% discount - register
now! Offer expires April 22*.

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to