Re: [openstack-dev] [Heat] workflow for fixes involving numerous changes

2013-12-10 Thread Zane Bitter
On 10/12/13 13:34, Clint Byrum wrote: Excerpts from Steven Hardy's message of 2013-12-10 03:00:26 -0800: On Tue, Dec 10, 2013 at 11:45:11AM +0200, Pavlo Shchelokovskyy wrote: - wouldn't it be better to keep all these changes in one bug and fix all misuses per file basis (with one file per patch

Re: [openstack-dev] [Heat] workflow for fixes involving numerous changes

2013-12-10 Thread Clint Byrum
Excerpts from Steven Hardy's message of 2013-12-10 03:00:26 -0800: > On Tue, Dec 10, 2013 at 11:45:11AM +0200, Pavlo Shchelokovskyy wrote: > > - wouldn't it be better to keep all these changes in one bug and fix all > > misuses per file basis (with one file per patch-set for example)? It seems > >

Re: [openstack-dev] [Heat] workflow for fixes involving numerous changes

2013-12-10 Thread Steven Hardy
On Tue, Dec 10, 2013 at 11:45:11AM +0200, Pavlo Shchelokovskyy wrote: > Hi all, > I am fixing assertions in unittests now (initially > https://bugs.launchpad.net/heat/+bug/1259023). I've seen that Clint have > split this bug into three separate bugs, one per assertion misuse type. As > these change

[openstack-dev] [Heat] workflow for fixes involving numerous changes

2013-12-10 Thread Pavlo Shchelokovskyy
Hi all, I am fixing assertions in unittests now (initially https://bugs.launchpad.net/heat/+bug/1259023). I've seen that Clint have split this bug into three separate bugs, one per assertion misuse type. As these changes will affect many files (practically every file in the tests), I would like to