[tootie]

For those of you with a big portfolio of apps, how do you handle framework updates? Scheduled housekeeping once a quarter? Ad hoc? Ignore them until a disaster happens then panic?

[collinmanderson]

I generally develop against django master with loud warnings. Whenever a warning comes up, such as `DEFAULT_AUTO_FIELD` not being specified, or a behavior change such as `SECURE_REFERRER_POLICY`, I go through and apply the same change to _all_ my projects at the same time.

So I'm applying minor changes to multiple projects at the same time as I become aware of the new changes. Once the new Django version comes out, they're basically ready to go live with the new version.

[frankwiles]

The necessary changes with your use of the framework are pretty minimal so it's easy enough to keep pace on about a quarterly basis.

Usually the only friction is if there is a third party library/app you're using that doesn't yet support the newer version of Django.