hi again @carchrae
have sent you a slack invite.
Re. spree upgrade, there are a couple of pages that outline proposed approach. It would be great if you could make a note / add advice on those pages so we can be sure it won’t get missed by the devs that pick it up?
Introduction
We’re currently using version 1.3.6 of Spree, which was released about 2.5 years ago. Since that release, substantial work has gone into Spree, and a number of major releases have brought it up to version 3.0. However, the upgrade process from version 1.3 to 2.0 (the next step for OFN) has proven challenging and very difficult to scope or estimate, which has prevented us from completing the upgrade.
Recently, shortcomings in the Spree 1.3 tax calculations have hindered development,…
This thread will serve as a progress report for the Spree upgrade.
Continued from Spree Upgrade: Purpose and Strategy
Step 1
Based off 432d129.
This step consists of biting off the first 133 commits out of 2308 needed to reach 2-0-stable.
Time thus far: 24 hours (includes project research and planning)
Failing specs remaining: 4
Update 16-9-2016:
Failing specs: 0
Testing:
Merged: 18-11-2016
Step 2
Find the number of the previous commit:
gl 2-0-stable~2175
# 432d129
Get SHA of nex…
Thread for test results for spree upgrade steps.
1 Like