[Openstack] SQLAlchemy migration number conflicts

Trey Morris trey.morris at rackspace.com
Wed Jun 1 19:47:37 UTC 2011


I like vish's idea. instead of 999, maybe it should be anything over 9000.

-tr3buchet

On Wed, Jun 1, 2011 at 1:47 PM, Brian Schott <bfschott at gmail.com> wrote:

> That's not crazy, but I'd recommend a range of numbers 900-999?  There have
> been cases where larger branches have multiple migrate files.
>
> Brian Schott
> bfschott at gmail.com
>
>
>
> On Jun 1, 2011, at 1:56 PM, Vishvananda Ishaya wrote:
>
> This might be a little crazy, but how about numbering new migrations 999
> and having tarmac rename the file before merging. Then all we need is a
> little logic in the migrate code to allow 999 for testing purposes.
>
> Vish
> On Jun 1, 2011 9:33 AM, "Brian Schott" <bfschott at gmail.com> wrote:
> > I was getting migrate errors because gaps are not allowed in the
> migration numbers. Maybe this could be changed so that folks could use
> arbitrarily large numbers in their branches until ready to propose for
> merge. That would help minimize conflicts and manual bzr rename on our local
> branches when merging from trunk.
> >
> > The reservation numbers need to be monotonically increasing at trunk
> merge because suppose migration 12 gets reserved but doesn't submit any code
> changes, then migration 13 comes in and gets approved and merged, then
> migration 12 merges code and breaks migration 13. You can't revert back to
> migration 11 because the new migration 12 is in the way.
> >
> > Brian Schott
> > bfschott at gmail.com
> >
> >
> >
> > On Jun 1, 2011, at 11:12 AM, Ed Leafe wrote:
> >
> >> Another option is to have a migration reservation page in the wiki. It
> would contain a table with a sequence of numbers in the first column, and a
> blank cell in the right column. When you need to add a migration, fill your
> branch name next to the first available number, and that number's yours. If
> there's a conflict, it will be clear who needs to change their number.
> >>
> >> It's a manual process, sure, but this isn't a process that's repeated
> all that often.
> >>
> >>
> >>
> >> -- Ed Leafe
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : openstack at lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help : https://help.launchpad.net/ListHelp
> >
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110601/89c8dd70/attachment.html>


More information about the Openstack mailing list