5 ms·
> I usually wait until the 3rd patch myself, after many years of paying the price of greedy upgrades. We wouldn't get there if everyone does that though.
by 4m1rk 4y ago
> I usually wait until the 3rd patch myself, after many years of paying the price of greedy upgrades.
We wouldn't get there if everyone does that though.
- fluidcruft 4y agoWhy not? Production isn't where bugs should be found. Plenty of time to test things before production.
- bravetraveler 4y agoTo be fair to who you're replying to, this did basically start with "new version -> production" Not much room left for integration/development and so on I pick these things up early in lower environments, as I suppose you do, so that the real production upgrade isn't scary... and we don't fall behind Waiting forever for the community to QA doesn't work, you probably aren't running exactly what they are
- 4m1rk 4y agoMaybe what I have in mind as the env setup is different but 1) lower envs might not experience the load or edge cases as prod 2) lower envs are supposed to be as similar as possible to prod. Is it a good idea to test things with Python 3.11 and run it in prod using a different Python version? It might even force you to use different versions of a lib for each env which means no confidence for releases to prod based on lower env tests (one way would be to have two lower envs. One for next Python version and another for current one as in prod. But #1 is my main issue.)