On 02/18/2013 03:15 PM, Salvatore Orlando wrote:
I'm fine with this, even if fixing the migration script is something
which will the require the reviewers just to rubberstamp the patches.
We can start filing a bug with critical or high priority and ensure it
targets G-3.
I agree
Salvatore
On 18 February 2013 14:01, Akihiro MOTOKI<mot...@da.jp.nec.com> wrote:
Hi,
Several patches contains db migration scripts and now we are merging several
patches.
It leads to branches in db migration scripts. In a usual process, we need to
rebase
the patch to catch up the latest, but it forces us to do another review and
approval.
How about having a special rule that we ignore branches in db migration scripts
until G-3 branch cut and fix the branches of db migration scirpts
just before/after the branch cut?
Thanks
Akihiro
--
Mailing list: https://launchpad.net/~quantum-core
Post to : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~quantum-core
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~quantum-core
Post to : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~quantum-core
More help : https://help.launchpad.net/ListHelp
