Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v2 1/1] Deal with upgrade mess in 2.0
Date: Wed, 13 Jun 2018 23:57:44 +0300	[thread overview]
Message-ID: <20180613205744.GG10632@chai> (raw)
In-Reply-To: <7ff57cf1d798b75817128da453cc08fc4004258b.1528563947.git.v.shpilevoy@tarantool.org>

* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [18/06/09 22:33]:
> Merge upgrade to 1.8.2/.4 into 2.1.0. Versions 1.8.2/.4 are
> broken because of invalid _trigger creation and deprecated
> versioning policy.
> 
> Vinyl/Xlog upgrade tests from 1.7.7 are broken too since they
> actually contains 1.8 snapshots, so remove them. Add the test on
> upgrade from 1.10 to ensure the new upgrade_to_2_1_0 works.

OK to push.


-- 
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov

      reply	other threads:[~2018-06-13 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 17:06 [tarantool-patches] " Vladislav Shpilevoy
2018-06-13 20:57 ` Konstantin Osipov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180613205744.GG10632@chai \
    --to=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH v2 1/1] Deal with upgrade mess in 2.0' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox