Sorry. I sent the wrong link. https://review.openstack.org/#/c/22405/
>>>>> Date: Wed, 20 Feb 2013 17:30:50 +0900 >>>>> From: Akihiro MOTOKI <mot...@da.jp.nec.com> >>>>> Subject: Re: [Quantum-core] branches on db migration scripts > > Hi, > > I uploaded the patch which fixes branches in db migration scripts. > Could you check it? > > This patch does not conflict with https://review.openstack.org/#/c/21963/ > (it is the only remaining approved patch). > > Thanks, > Akihiro > > >>>>> Date: Mon, 18 Feb 2013 09:19:20 -0800 > >>>>> From: Dan Wendlandt <d...@nicira.com> > >>>>> Subject: Re: [Quantum-core] branches on db migration scripts > > > > Sounds good. Mark, I'm fine if this commit happens after the G-3 branch > > deadline tomorrow night, > > as we can always cherry-pick individual commits. > > > > dan > > > > On Mon, Feb 18, 2013 at 8:44 AM, Akihiro MOTOKI <mot...@da.jp.nec.com> > > wrote: > > > > I filed a bug as a reminder. > > https://bugs.launchpad.net/quantum/+bug/1129260 > > Now it is assigned to me. Feel free to take it if you want. > > > > "quantum-db-manage upgrade grizzly" sounds nice! > > > > Akihiro > > > > (2013/02/18 23:52), Mark McClain wrote: > > > > I'm ok with it. My plan was to clean up the migration branches > > tomorrow afternoon. I was > > also going to create a no-op migration called grizzly so that > > deployers could init their > > folsom db with "stamp folsom" and then run "upgrade grizzly" > > > > mark > > > > On Feb 18, 2013, at 8:15 AM, Salvatore Orlando > > <sorla...@nicira.com> 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. > > > > 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 > > > > -- > > 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 > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Dan Wendlandt > > Nicira, Inc: www.nicira.com > > twitter: danwendlandt > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > -- > 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