Re: [openstack-dev] [puppet] Midcycle Sprint Summary
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 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 deprecations when I could. First round was done > which was the removal of old code previously deprecated and I have > started on a second pass which is new deprecations that are being > introduced in Mitaka by upstream cinder. > > This is the fist time I've sat down to actually just hunt and implement > deprecations and the number one thing I learned is that it is really > time consuming. We'll need several people working on this if we want > them complete for every module by release time. > > > -- > Cody > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [puppet] Midcycle Sprint Summary
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). https://github.com/openstack/puppet-openstack_spec_helper/blob/master/run_unit_tests.sh https://github.com/openstack/puppet-openstack_spec_helper/blob/master/run_beaker_tests.sh They run in our CI but you can also run it on your laptop. * (still in progress) CI jobs for puppet-openstack-cookiecutter. https://review.openstack.org/272156 https://review.openstack.org/272146 * Introducing Release notes management with openstack/reno, in puppet-keystone. http://docs.openstack.org/releasenotes/puppet-keystone/ See https://review.openstack.org/274409 for examples of release notes. * Enabling voting for our integration jobs * Optimize CI jobs runs to reduce nodes consumption https://review.openstack.org/#/c/274137/ * Improve puppet-ceph module: make puppet runs idempotent on centos7 * Cleanup old deprecations & old backward compatibility stuffs * a lot of old patches were rebased, reviewed and some of them merged. I'm sure I missed something so feel free to complete the list. Thanks a lot for your participation and this outstanding work, https://goo.gl/2mwmKy -- Emilien Macchi signature.asc Description: OpenPGP digital signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [puppet] Midcycle Sprint Summary
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 deprecations when I could. First round was done which was the removal of old code previously deprecated and I have started on a second pass which is new deprecations that are being introduced in Mitaka by upstream cinder. This is the fist time I've sat down to actually just hunt and implement deprecations and the number one thing I learned is that it is really time consuming. We'll need several people working on this if we want them complete for every module by release time. -- Cody signature.asc Description: OpenPGP digital signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev