Platform Team Week of January 27th, 2013

[Andy Parker]

Week of January 27th, 2013

** Next PR Triage Wednesday, February 5th. **

Priorities

  1. Work toward Puppet 3.5.0 (https://tickets.puppetlabs.com/browse/PUP/fixforversion/11009)

  2. PE 3.2 support

  3. Ability to list dynamic environments (PUP-536)

  4. Facter 2.0 implementation (PUP-552)

  5. Squash bugs uncovered by automated tests

Commentary

Adrien and Kylo have continued on the Facter 2 front. A lot of things have wound down, but there are still tweaks and other small changes going into that work. According to Kylo it looks like they are still on track for a mid-February release.

The 3.5.0 version of the new environment structure is shaping up. Joshua and I merged a few changes over the week, and there are a few more items that we need to clear up. This isn't the end of the feature, there are still a lot of ideas for how to extend it to directly cover more use cases (e.g. more flexible modulepath).

Peter, Ethan, and Josh have been uncovering and tackling various stability issues. Most of these issues have been related to ruby bugs and memory corruption. This work wasn't directly planned, but was uncovered when investigating failures in our automated tests. Sometimes to failures that come and go a real bugs!

Changes Moving Forward

None

Data

Trying out some different data this time. With the change to not having Adrien dedicated to handling contributions I'm going to start publishing a snapshot of the pull request metrics so that we can see if there are any unwanted consequences.

http://pullrequestmetrics.herokuapp.com/

--

Andrew Parker

an...@puppetlabs.com

Freenode: zaphod42

Twitter: @aparker42

Software Developer

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14

[Joshua Hoblitt]

On 02/03/2014 10:56 AM, Andy Parker wrote:
>
> Trying out some different data this time. With the change to not having
> Adrien dedicated to handling contributions I'm going to start publishing
> a snapshot of the pull request metrics so that we can see if there are
> any unwanted consequences.
>
>
> http://pullrequestmetrics.herokuapp.com/
>

It would be interesting to see the merged/closed stats graphed for PL
and community separately. The % closed looks to be about the same as
the % of PRs sourced from the community. :)

-Josh

--

[Adrien Thebo]

You can actually click on different parts of the graphs to do filtering; for instance you can click on the `community` portion of the pie chart to only view metrics about community. Keep in mind that it's pretty common for us to fixup commits ourselves and merge those instead of merging the pull requests outright so that we can get necessary fixes in without having to ask the contributors for every minute change we want. Because of this the reported merge rate for community contributions is much lower than reality.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/52EFFE1B.6080906%40cpan.org.
For more options, visit https://groups.google.com/groups/opt_out.

--

Adrien Thebo | Puppet Labs