Platform Team Week of June 2nd, 2014

[Andy Parker]

Week of June 2nd, 2014

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

Priorities

  1. Puppet 3.6.2 with to fix some major problems reported against 3.6.1

  2. Puppet 3.7.0/4.0.0 with the final language polish as well as many other changes.

  3. Windows stability improvements

  4. CFacter on the march

Commentary

Sorry for the late update. I got caught up in meetings yesterday and then tried to make some progress in PUP-514.

The last few items for 3.6.2 have wrapped up and you should see 3.6.2 appearing any time now.

I feel like we've been falling behind in our pull request handling. The hangouts on Wednesdays have been a great forum for talking over and making decisions about them, but we haven't been too great about actually following through all of the time. To be honest it is a problem of cost :( It actually takes us a lot of effort to get changes in. Most of this comes down to unforeseen consequences of the changes. Some of this we discover in review (which takes time), some we discover when all of our tests get to run against the changes. I'm not sure what I can be done right now to lower the cost. The other possibility is that I'm off base here and we are keeping up just fine :)

Data

http://pullrequestmetrics.herokuapp.com/

--

Andrew Parker

an...@puppetlabs.com

Freenode: zaphod42

Twitter: @aparker42

Software Developer

Join us at PuppetConf 2014, September 22-24 in San Francisco

Register by May 30th to take advantage of the Early Adopter discount —save $349!

[Henrik Lindberg]

On 2014-10-06 17:37, Andy Parker wrote:
> Week of June 2nd, 2014
>
> ** Next PR Triage Wednesday, June 11th @ 10:00 am Pacific. **
>
> Priorities
>
>

> 1.. Puppet 3.6.2 with to fix some major problems reported against 3.6.1

> 2. Puppet 3.7.0/4.0.0 with the final language polish as well as many
> other changes.
> 3. Windows stability improvements
> 4. CFacter on the march
>
> Commentary
>
> Sorry for the late update. I got caught up in meetings yesterday and
> then tried to make some progress in PUP-514.
>
> The last few items for 3.6.2 have wrapped up and you should see 3.6.2
> appearing any time now.
>
> I feel like we've been falling behind in our pull request handling. The
> hangouts on Wednesdays have been a great forum for talking over and
> making decisions about them, but we haven't been too great about
> actually following through all of the time. To be honest it is a problem
> of cost :( It actually takes us a lot of effort to get changes in. Most
> of this comes down to unforeseen consequences of the changes. Some of
> this we discover in review (which takes time), some we discover when all
> of our tests get to run against the changes. I'm not sure what I can be
> done right now to lower the cost. The other possibility is that I'm off
> base here and we are keeping up just fine :)
>

Just for fun, I looked at the stats in the app below and we are right
now on par with our best months historically. We have had a more steady
flow of PR resolutions compared to 2012 up to may 2013. (March 2013 was
our worst month). (There is a slider at the bottom of the page that
allows you to see all historical data).

May - June the average lifetime of a PR is around or less than 10 days.
I think that means we are doing amazingly well !

This is somewhat unscientific as it is calculated on all PRs (including
those from Puppet Labs). Still, in relative terms, it has almost never
been better.

- henrik

> Data
>
>
> http://pullrequestmetrics.herokuapp.com/
> Inline image 1

> Inline image 2
>
> --
> Andrew Parker

> an...@puppetlabs.com <mailto:an...@puppetlabs.com>

> 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 puppet-dev+...@googlegroups.com
> <mailto:puppet-dev+...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/CANhgQXskv8CEQEf0g0rwDsraFb_RvwL%2BFuvsKBVqsvfYPXG9fg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CANhgQXskv8CEQEf0g0rwDsraFb_RvwL%2BFuvsKBVqsvfYPXG9fg%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/

[Felix Frank]

On 06/10/2014 05:37 PM, Andy Parker wrote:
> I feel like we've been falling behind in our pull request handling.
> The hangouts on Wednesdays have been a great forum for talking over
> and making decisions about them, but we haven't been too great about
> actually following through all of the time. To be honest it is a
> problem of cost :( It actually takes us a lot of effort to get changes
> in. Most of this comes down to unforeseen consequences of the changes.
> Some of this we discover in review (which takes time), some we
> discover when all of our tests get to run against the changes. I'm not
> sure what I can be done right now to lower the cost. The other
> possibility is that I'm off base here and we are keeping up just fine :)

Well, I think the only new ones we tackled today were some Facter PRs
and that on from cprice. So yes, we're getting relatively little headway
(although, we *did* manage to merge many of the held over ones).

Perhaps we need to keep a more strict discipline and not allow ourselves
to get derailed, at least as long as there is a significant number of
unreviewed PRs.

Mind you, I do enjoy the side discussions and am prone to start those
myself, still - we may want to restrict ourselves a little depending on
the overall respective PR situation.

Cheers,
Felix