Django's API Stability Policy for Crispy Forms

Django itself doesn't have an easy way to do a quick survey other than, yeah, you don't want to change it and then people raise their hand afterwards. There's not capacity there to maintain some sort of API stability policy of the likes of Django's. You know, we've got crispy forms long term. No, we haven't got a crispy term. Sometimes it will. If they're going to upgrade, they can just add an extra dependency and maybe change a line in the settings file. And if there's a we breakage, well, sorry, but this isn't a big package. It's maintained by David. I'm still helping out from where I