Plan for next release - v2.0

[samuelhwilliams]

Opening this to think about/plan for the next release, which I propose should encompass:

• The changes merged after v1.6.1 and up to when flask-admin was moved under pallets-eco

Plus these changes merged since:

• Replace inspect.getargspec() that was removed in Python 3.11 #2397
• Fix value of desc param in filter form (1 instead of "True") #2265
• Support mongoengine.DateField sorting #2114
• Use correct file in examples/bootstrap4 #2416
• Tuple field_flags are deprecated #2341
• Fixes #2406: Multiple requests are sent when opening create, edit, and detail modals due to repetitive load of bs4_modal.js #2407
• String null fix #2321
• Fix already exists translation #2464

Plus these target changes:

• Removing python 3.7 support and adding python 3.12: Remove python 3.7 compatibility; add python 3.12 #2453
• Removing Flask-BabelEx support and moving back to using Flask-Babel: Replace Flask-BabelEx with Flask-Babel #2460
• Flask host_matching support: Add Flask host_matching support to admin instances #2461
• Allow configuring FLASK_ADMIN_SWATCH per admin instance: Pull together all Flask-Admin theme configuration #2462
• Standardise app.config names: Use FLASK_ADMIN_ prefix for all app.config configuration #2472
• SQLAlchemy 2 compatibility (@cjmayo): SQLAlchemy 2.0 Compatibility #2483
• Flask 3 compatibility (@cjmayo)
• WTForms 3 compatibility (@cjmayo)
• Remove bs2 and bs3: Remove bootstrap 2 and 3 #2474
• More clearly define our dependencies/versions: Dependencies via pip extras #2476
• Customise and prevent arbitrary user-overrides of page_size: Allow customising page_size options, and prevent arbitrary page sizes #2479
• Support CSP: Support Content-Security-Policies via nonce values #2480
• Remove appengine support #2481
• Remove any existing DeprecationWarnings

And potentially any other small PRs we think we can get in fairly easily.

When the changeset is locked

• review and update documentation for anything that's been missed
• write a changelog entry: https://github.com/pallets-eco/flask-admin/pull/2499/files

---

Because of those last target changes, we'd need to do this as a major version bump.

@aenglander @Abdur-rahmaanJ - thoughts?

[Abdur-rahmaanJ]

@samuelhwilliams How about 1.7?

[samuelhwilliams]

What makes you suggest 1.7?

I think standard practice would be to assume Semantic Versioning, which says breaking changes should be a major versioning bump (ie 1 to 2). Dropping python 3.7 and dropping flask-babelex are breaking changes, so I think V2 would be the logical step to me.

Happy to hear counter arguments though.

[Abdur-rahmaanJ]

Good then did not see any breaking changes from the description. Good 👍 for a 2.0.

[hasansezertasan]

I believe #2407 is suitable for the next release.

[samuelhwilliams]

Flask-Babel and host_matching PRs are up. Will leave open for feedback for a few days.

Aiming to do a 2.0.0rc0 release next week ish.

[samuelhwilliams]

Right. We have a bunch of stuff merged - I'm thinking of doing a 2.0.0rc0 release, maybe tomorrow. That would mean (in my head) no more feature merges - only bug fix merges - until 2.0.0 proper is released.

Do we think we want to try to get anything else simple/quick in urgently before the rc0 release?

[samuelhwilliams]

@cjmayo Have added SQLAlchemy 2/Flask 3/WTForms 3 as target changes for a 2.0.0 release, if you're happy with that? I'm happy to try to help where needed, although it looks like maybe you've got it covered.

[princerb]

There are more configuration changes too, like when creating Admin instance, so I guess it is fair to think about the next release tagging with 2.0.0

[cjmayo]

@cjmayo Have added SQLAlchemy 2/Flask 3/WTForms 3 as target changes for a 2.0.0 release, if you're happy with that? I'm happy to try to help where needed, although it looks like maybe you've got it covered.

I'm happy. I think I have enough - at least to get the tests to pass (I have been using these patches for a while with the new dependencies).

[samuelhwilliams]

Would you like to weigh in/mind weighing in on #2476? It deals with dependencies too, specifically making it more explicit what dependencies are required for certain features and what versions we support. It doesn't do much work bumping dependencies, but should make it easier to test+validate dep bumps in the future.

[samuelhwilliams]

Ok - the target date is obviously slipping a bit, but I think it's useful to get a few more of these things in before doing some kind of pre-release.

Notably:

• CSP support
• Decide on whether we deprecate flask-mongoengine, or how we support it if we're keeping it

[ElLorans]

Can we have in the docs a suggested approach for considering client's timezone when submitting datetime fields? I am referring to #1892

[samuelhwilliams]

@ElLorans would you like to put up a PR adding some information and/or an example? I think specifically an example would be super helpful :)

[ElLorans]

@samuelhwilliams just opened #2502

[samuelhwilliams]

Since the changes merged so far for v2.0.0 include a lot of dependency bumps, I think it also makes sense to switch the S3 admin interface over from using boto to boto3, and the azure-blob-storage interface to using azure-storage-blob>=12. So will try to include those as well.

[pajusmar]

Thank you for all the hard work on the new release. I noticed that while there are many exciting updates mentioned, there hasn't been any discussion about the state of translations. There was an earlier issue (#1950) that raised concerns about updating translations, and I was wondering if this has been addressed in the latest release or if there are any plans to do so.

[samuelhwilliams]

Hey @pajusmar - it's a good question. I've asked it on the pallets-eco discord to work out what our plan is with translations... 👀