No, we should have every day as review day. If there's code waiting to be reviewed that addresses a bug or a feature, there's simply no good reason to write new code for a different bug or feature with the same priority until the code that's already out there is reviewed.
On Fri, Jun 20, 2014 at 11:16 AM, Andrew Woodward <[email protected]> wrote: > Should we also have the 25th as review day so we can squish those down too? > > On Fri, Jun 20, 2014 at 6:30 AM, Mike Scherbakov > <[email protected]> wrote: >> Fuelers, >> we need to group and enforce bug squashing activities on Tuesday, as >> discussed on IRC meeting this Thursday [1]. Feel free to do bug triaging >> first on Monday if needed. >> We have lots of bugs, and to meet quality criteria for the release we really >> need this. >> >> Every dedicated Fuel developer should stop all other activities and dedicate >> this day to bugs only. Follow instructions from last bug squashing day [2]. >> Among other bugs, please give the higher priority to those with >> "customer-found" tag. >> >> Please, use #fuel-dev for synchronization. I'll be on vacation, but I'll let >> Dmitry Borodaenko to lead all bugs related activities, he is Bug Master for >> this release :) >> >> [1] >> http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-06-19-16.00.log.html >> [2] http://lists.openstack.org/pipermail/openstack-dev/2014-June/037746.html >> >> Thanks, >> -- >> Mike Scherbakov >> #mihgen >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Andrew > Mirantis > Ceph community > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
