Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When will you release support for mui v5.0 #349

Closed
animaonline opened this issue Sep 22, 2021 · 6 comments
Closed

When will you release support for mui v5.0 #349

animaonline opened this issue Sep 22, 2021 · 6 comments
Labels
question Further information is requested

Comments

@animaonline
Copy link

No description provided.

@animaonline animaonline added the question Further information is requested label Sep 22, 2021
@doctorallen
Copy link

There is support for MUI v5.0 in the prerelease branch. You can install it with:

Yarn

yarn add @material-table/core@next

NPM

npm install @material-table/core@next

Read more here.

@animaonline
Copy link
Author

thanks a bunch!

@LuchoTurtle
Copy link
Contributor

@doctorallen Are new PRs made in the master branch merged into the next branch? For example, I recently made a PR that was merged yesterday and I'm needing to migrate to MUI v5 and it would be amazing if the PR would also be available in the next branch!

@sm3sher
Copy link

sm3sher commented Sep 24, 2021

Yes, the next branch seems to be up-to-date with the master branch.
I'm also migrating and hoping that the master branch will support MUI 5 very soon.

@Domino987
Copy link
Contributor

So just fyi so everybody is on the same level. Yes as already mentioned the master and next branch are kept up to date with each other.
Regarding supporting v5: we are currently in the spot of supporting either or. So the master is V4 and next is v5. Until a large enough number of people moved to v5, merging next into master would prevent all V4 users from receiving more updates. So I am not sure when a good time would be to force this but also how long we should await the migration from others users. Do you guys have a good idea about this?

@LuchoTurtle
Copy link
Contributor

According to MUI's blogpost, they have stopped supporting MUI v4 themselves and seem to be fully focused on v5 onward.

"we stopped all development on v4 as soon as we started to work on v5"

So, it would make sense pragmatically to keep in line with what they're doing and focus on MUI v5 and stop supporting v4. However, it wouldn't hurt to wait a wee so more users migrate to v5. I can't really tell how much time you should wait but, to me, it isn't insensitive to merge next into master right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants