Commit 610bad24 authored by Kirill Smelkov's avatar Kirill Smelkov

v↑ tempstorage(ZODB4) 2.12.2 -> 3-nxd

In 6e696faa "v↑ tempstorage 2.12.2 -> 5.2(ZODB5) 3-nxd(ZODB4-wc2)" we upgraded
tempstorage for ZODB5 and ZODB4-wc2, but were careful and left tempstorage,
that was being used with ZODB4, intact. However @tomo suggests that we should
also upgrade tempstorage for ZODB4 because of the loadBefore fixes and not to
further grow divergence in between ZODB4 and ZODB4-wc2:

    I understand that keeping the same version of tempstorage for ZODB 4 is to
    be on the safe side but I'd rather change it to tempstorage4-wc2 anyway. I mean
    we have a bugfix but we are afraid to apply it. Also, The less difference
    between ZODB 4 and ZODB 4-wc2 the better (everything will be more tested this way).
    ( nexedi/slapos!1009 (comment 137985) )

-> So let's do that.
parent 6e696faa
......@@ -45,14 +45,6 @@ eggs = ${:egg}
egg-versions =
tempstorage = 5.2
# tempstorage4 is plain upstream egg, but better be changed to be the same as
# tempstorage4-wc2 because of loadBefore fixes.
[tempstorage4]
<= tempstorage5
egg-versions =
tempstorage = 2.12.2
# tempstorage4-wc2 is tempstorage 3 + backports for loadBefore fixes
[tempstorage4-wc2]
......@@ -69,3 +61,8 @@ branch = 3-nxd
revision= 77b49295db78
location = ${buildout:parts-directory}/tempstorage
git-executable = ${git:location}/bin/git
# tempstorage4 is the same as tempstorage4-wc2 because of loadBefore fixes.
[tempstorage4]
<= tempstorage4-wc2
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment