v7 workflow

[tabacitu]

Hey @pxpm , @karandatwani92 , @jcastroa87 - heads-up.

I've just:

• created a v7-dev directory in Docs
• created a v7 branch in CRUD
• created a v3 branch in PRO

We can start adding things to v7. Please note:

• we work EXACTLY the same way as we do for main; the branches are protected;
• we submit PRs to the v7/v3 branch with a corresponding PR for the docs (include in upgrade guide if needed);
• all breaking changes need to be reviewed and merged by me;
• every once in a while we need to pull changes from main to v7;

---

For reference (and anybody wondering), here are the bigger changes we plan to launch in v7. It's a maintenance release, so not a lot. Even in this new version, we want to keep breaking changes to an absolute minimum... and keep 99% of all project with a sub-5-minute upgrade guide (the time it takes to read it).

New Features

• CRUD lifecycle hooks
• 2FA
• re-usable filters
• command & docs to generate CRUD tests (Laravel Dusk)
• (may be too big) livetable component (uses Livewire and our existing columns)
• (may be too big) export operation

Breaking changes

• fixed uploaders
• ckeditor & tinymce separated into individual packages
• drop support for L10 (maybe)
• fixed basset
• parent theme (Bootstrap) in CRUD

---

Let's do this 💪

[tabacitu]

PS. Once everybody in the team has read this, feel free to delete.

[pxpm]

I've just tagged it next-version so it does no screw our issue report 👍