Open Reviews from the etherpad: Nova(lots), Neutron(2), Keystone(2), Glance(1), Ironic/DevStack(1) reviews
I went through, checked all the reviews listed and put a notation on state of the patches, next steps, etc. Take another look. (my comments are medium blue). Some reviews are ready for cores, some are actively iterating. Please check there. If the associated bug is not linked to the review, please let the developers know. Thanks so much. I think these will make Liberty and the first Kilo maintenance releases much better. Also, this means that if you think the patch is backport potential, make sure that it is tagged as such. I think this has been a great success for the Chinese developers who participated and for OpenStack in general. I think future China Hackathons need to better coordinate timing, but for a first effort, I think this is a success. Any other opinions out there? Thanks so much. --Rocky -----Original Message----- From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] Sent: Friday, April 17, 2015 09:53 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova][Neutron] HELP -- Please review some Kilo bug fixes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/16/2015 09:54 AM, Bhandaru, Malini K wrote: > Hello Nova and Neutron developers! > > OpenStack China developers held a bug fest April 13-15. Worked on > 43 bugs and submitted patches for 29 of them. Etherpad with the bug > fix details (at the bottom): > https://etherpad.openstack.org/p/prc_kilo_nova_neutron_hackathon > > Their efforts to make the Kilo release better can reach fruition > only with your reviewing them. Cores and PTLS, would really > appreciate your help. > > In addition to making Kilo stronger, you will be acknowledging and > motivating our China OpenStack developer community. > I've walked thru the list to see whether there is anything reviewable for neutron. It's all either merged, or launchpad bugs don't link to any patch in review. So there was nothing for me (as a neutron developer) to help with. Maybe I missed something, in that case Doug's suggestion to create a clear per-project list of actionable patches is valid. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVMTpjAAoJEC5aWaUY1u57KI0H/RRcTu07sRrIjJBYzhAL2jkD bdWF+8kbyG2bKIxl+5vxIgWjCXJlXw4YYilSWQ0lKyq+Q2Jvlx8Kt975O1RJNKa/ rY8f9gVzHsroyrpb5/WSc1hsNahqiBwwP2aUoEbqtvueKNjEfM3BW8zrVZzuq8Wm NckdhRTF3Nfzu3ZFeW23EtVcnZ8SE7o3+OGFFnJSmW8h6mTePyJKUKoEGlNEopDm wCnFjB3GgMQJl8E2Y/31xEJx1S6FHiMm7Zk5wPadO/LsBvMyTMBFZ1DsReBB4EQB LspNMYCHqJcnebN3hj/OWqlUfu9jzqA3U1qW+W722Bp99MoavF7UG7LEffrGgk8= =f+XH -----END PGP 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 __________________________________________________________________________ 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
