Re: [openstack-dev] [puppet] Midcycle Sprint Summary

2016-02-02 Thread Matt Fischer
Perhaps we should cover and assign each module in the meeting after the release? Actually removing the code and tests in many cases would be a good assignment for people trying to get more commits and experience. On Feb 1, 2016 2:22 PM, "Cody Herriges" wrote: > Emilien Macchi

[openstack-dev] [puppet] Midcycle Sprint Summary

2016-02-01 Thread Emilien Macchi
Last week, we had our midcycle sprint. Our group did a great job and here is a summary of what we worked on: * Make good progress on bug triage & bug fixing. ~25 bugs were triaged. * Unit & Functional testing for puppet-openstack-spec-helper (jobs are voting).

Re: [openstack-dev] [puppet] Midcycle Sprint Summary

2016-02-01 Thread Cody Herriges
Emilien Macchi wrote: > Last week, we had our midcycle sprint. > Our group did a great job and here is a summary of what we worked on: > My attention at the office was stolen quite a few times by finishing up work for our production cloud deployment but I worked on the pupept-cinder Mitaka