The author has opted to use Django and would like to get to a state where their app is essentially "completed" -- where it will work fine without having to touch it again or make major changes.

The conflict arises because Django has a stated mission to always be improving (like a perfectionist). This causes issues for the author when they have to re-write parts of their application in order to keep up with updates to the mainline framework.

The author would like be able to get things like security fixes and performance improvements without breaking changes -- whereas the Django team is willing to require breaking changes in pursuit of improvements.

Ultimately, the author may be better served by using tools/frameworks that are considered "completed" (examples might be things like jQuery) or have a maintenance philosophy that prioritizes backporting and compatibility over improving the features/experience.

Oh I see.

Software is a living thing - it needs to keep up with the technologies it is built on for a whole bunch of reasons.

Some software of course can be "complete" but that tends to be pretty specific stuff with a very defined scope.

To get security fixes they have to update to new versions, which requires them to change their code, but they don't want to have to change their code once it's done.