Stephen
(Stephen)
May 14, 2019, 12:45pm
9
That’s the point, stable in this sense means ‘infrequently changed’.
There’s good reason that so many communities are on tests-passed, including CDCK’s own hosted customers.
For the mini-racer issue, it has been resolved in this commit: FIX: We need a newer mini_racer for ruby 2.6.3 · discourse/discourse@99dd426 · GitHub
spajus:
I’m not the forum dweller type myself. Usually it’s faster to find a solution to a problem on my own than to post and discuss it in dev forum. This time I just had to vent, with hope that discourse devs would introduce some versioning to all components, and my life would get easier for next upgrade
I don’t think you’ve made your experiences any easier by taking this tact.
spajus:
P.S. I always do upgrades in a clean VM, by first reproducing my current environment, restoring production backup, testing that it works, then upgrading it there to see if upgrade doesn’t fail. It always fails. Maybe I’m just really unlucky.
How do you repro your production environment exactly? If you aren’t running a staging copy in parallel you run a very high risk of just introducing more variability here.