3 ms·
I work in the Rails world, and perhaps my perception is colored by the big changes they tend to make, but this seems like more of a minor than a major version r
by bdcravens 3y ago
I work in the Rails world, and perhaps my perception is colored by the big changes they tend to make, but this seems like more of a minor than a major version release? Or is this relatively big for Django?
- iamsanteri 3y agoI'd be also interested to hear someone proficient have an opinion about this. A 5.0 update sounds like something big. What about the rest of the async parts in Django having been in the process of being re-written since a while, as I've heard? Also has it ever been considered to build some deeper integration of Celery for enabling and handling in-memory background job processing in a more closely and "better-integrated" way akin to Rails' active job?
- Humphrey 3y agoYes, relative minor update. Django is very mature and does most things needed, so there has not been need for major changes since about 2.0. Django releases are now based on a schedule, so the 5.0 label wouldn't have been chosen because of significant changes. But, I have observed that releases often look like this: - X.0 Newer shinier features - X.1 More refinement and minor features - X.2 [LTS] More refinement and minor features Which means if you stick to the point 2 releases you get longer support and subjectively more stability since the shiny new features have been polished over a couple of point releases. But in reality these days, I think it's just whatever features are ready to ship for the scheduled release date.