Rollout of v5 🚀

[flaviendelangle]

This issue is here to discuss what we should finish before release the 1st stable version of the v5.

The issues we decide to include in the v5 will be listed in the v5 milestone

---

To summerize, the v5 version only supports the v5 version of the core (no more @material-ui/[email protected], see Migration Guide)

[flaviendelangle]

The ambitious features yet to be finished are:

• [DataGrid] Change virtualization implementation #1933 @m4theushw, do you intend to finish it before the launch of the stable version ?
• [core] Each feature hook should initialize synchronously its state #2293 @flaviendelangle, ready for review
• [docs] Generate docs for components #2465 @m4theushw
• [DataGrid] First class support of v5 #1902 , @DanailH, I have assigned it to you since you are doing Replace @mui/styles with @mui/system #1234 which is the only issue related to it in the millestone
• [core] Implement tree-based row management #2813 @flaviendelangle

Other smaller tasks:

• Rename all selectors to match the naming format used on most of them (ex: gridFilterStateSelector, gridFilterModelSelector, gridVisibleRowsSelector, gridSortedVisibleRowsSelector, etc...). I have some renaming done in [core] Each hook should initialize its state synchronously #2572 , [core] Use selectors instead of direct state access in feature hooks and components #2723 and I'll do a last PR to rename the remaining ones.
• Prefix the props and API methods we may want to break before the next major with UNSTABLE if there are some

Do we have other topics we want to finish before the release ?

[DanailH]

@flaviendelangle thanks for the summary. I checked the linked issues but I don't think that the v5 release is dependant on all of them.
For example this one:

• [DataGrid] Print export [DataGrid] Print export #2519 @DanailH
  It is not really related to v5. It's a standalone feature. There set are ok, I think as they involve potential breaking changes

On another note - we can just repurpose this one #1902 and add/link all the relevant issues (maybe you already discussed it on Friday during the retro). I think we should aim to avoid having multiple tickets to track the same thing.

[flaviendelangle]

For #2519 their is nothing that forces us to merge it before the major release.
I think it will be merged before because we have 3 issues (#1902 , #2293 and #1933) that must be merged before the release. #1902 to be consistent with the core and the two others because they should cause a lot of small breaking changes / behavior changes and it would be better to do them before the major. So the major swill probably not be in the next 2-3 weeks, which gives us time.

EDIT : With that being said, I removed #2519 from the list as it is not a requirement for the release

[jacksteves]

Any chance #193 could be included? Thanks!

[flaviendelangle]

@JStevens127, we only add to the millestone things that would cause breaking changes.
#193 should not cause any.

But I think it is the next product feature we are going to focus on, so it should not take too long before being release.
We release every week or every two weeks so whenever the feature will be ready, it will quickly be released.

[flaviendelangle]

I added #2813 in the milestone because it's a breaking change on the selectors.

[oliviertassinari]

v5 is now officially released https://github.com/mui-org/material-ui-x/releases/tag/v5.0.0.