Rollout of v5 🚀

[oliviertassinari]

This issue is a follow-up on #20012 now is time to keep track of the final steps required to ship v5! This effort is part of the OKR Q3 2021: Release v5. It also concretizes Rollout-strategy into actionable engineering work. The strict minimum seems to be the following steps, where the order matters:

The ? are for items we might not do, depending on the strategy we pick or the bandwidth.

From v5.0.0-beta to v5.0.0-rc.0

Target: End of August

• Rename the packages Rename the packages #27666
• Add for rename the packages codemods
• Publish the v5.0.0-rc.0 packages
• Deprecate the last v5 beta releases with a link that expands on the new names of the packages. e.g. https://www.npmjs.com/package/@material-ui/core/v/5.0.0-beta.5

From v5.0.0-rc.0 to v5.0.0

Target: Early September

• Implement the new homepage [website] Improve homepage rebranding #27663
• Implement the new pricing page [website] Add pricing page #27598
• Implement the new about us page [website] Add about page #27599
• Close all the tickets in the v5 milestone. The ones we don't need can be labeled and removed from the milestone or moved to the v5.1 milestone.
• Wait at least a week until the next release
• Get the release blog post ready to publish
• Push the master branch to the v4.x branch (keeping master)
• Make the docs of v4 available at https://v4.material-ui.com/
• Push the next branch on the master branch (keeping next)
• Use the new branding pages over the older ones
• Update the links to point to mui.com instead of material-ui.com
• Update all the <!-- #default-branch-switch --> links
• Get the product hunt page ready to publish

Release day

A Wednesday, early afternoon is ideal

• Set https://mui.com/ the primary domain instead of https://material-ui.com/ on Netlify.
• Change social media covers and profile pictures
• Publish v5.0.0 on npm
• Publish the new docs on the TLD
• Release the changelog on npm
• Publish the v5 blog post
• Update Google Search console main domain
• Share the blog post on Twitter

Post stable v5.0.0

• Put https://v0.mui.com/ back online.
• Set 301 redirections https://next.material-ui.com/ to https://material-ui.com
• Set 301 redirections from the pages on material-ui.com to mui.com
• Update all the mentions to the @material-ui emails to @mui
• Release the other product pages, core, x, templates, design kit
• Update the Algolia search index to search on the right domain Support new domain algolia/docsearch-configs#4599
• Remove old subdomain in https://app.netlify.com/teams/mui/dns/material-ui.com
• Refresh the design of the documentation
• Clean up the versions a single branch of v4 should be enough, not one for each v4 minors
• Update https://codesandbox.io/s/styled-components-interoperability-w9z9d
• Update https://codesandbox.io/s/4j7m47vlm4?from-embed=&file=/package.json
• Deprecate all the versions of the older packages on npm Update the README.md files of the older versions to contain the link to the specific version docs and add info for v5 [@mnajdova]
• Delete the next branch [@oliviertassinari]
• Remove https://material-ui.com/discover-more/team/#team and add 301 redirection to https://material-ui.com/about. [@mnajdova]
• Migrate https://material-ui.com/store/contributors/material-ui/ to https://material-ui.com/store/contributors/mui/ https://github.com/mui-org/mui-store/commit/d7e7a6a10430d1712eecb8b25582ce705b06e2ab
• Migrate https://material-ui.com/store/contributors/material-ui-oss/ to https://material-ui.com/store/contributors/mui-community/ https://github.com/mui-org/mui-store/commit/91231c6827b87c63ff9dc7d16c8e9c3c61552101
• Google Suite workspace change primary email from @material-ui to @mui [@oliviertassinari]
• Rename https://opencollective.com/material-ui to https://opencollective.com/mui [@oliviertassinari]
• What should we do with StackOverflow? https://stackoverflow.com/questions/tagged/material-ui
• Fix the SEO issues reported by moz.com [@mnajdova]
• Deprecate the whole @material-ui/core package
• Run a full SEO crawling with ahrefs to make sure the linking of the pages is sound. [@mnajdova]
• Migrate Twitter account to the new name https://twitter.com/MUI_hq
• Migrate the repositories mui-org/material-ui → mui/mui-core and mui-org/material-ui-x → mui/mui-x
• Update the link that points to GitHub mui-org/*
  cc @mui-org/core
• Update https://nextjs.org/showcase/material-ui [@mnajdova] - Companies / Sites using Next.js vercel/next.js#10640 (comment)
• Migrate the store from https://material-ui.com/store/ to https://mui.com/store/, revert [website] Revert store URL to material-ui.com/store #28365 [@oliviertassinari]
• Rename the sites on Netlify, for instance, https://app.netlify.com/sites/material-ui-store/overview -> https://app.netlify.com/sites/mui-store/overview (what will we gain with it?)

[mwskwong]

We previously heard of @mui/joy, a new design system/theme. I believe the default look of it will be similar to what we currently have in https://mui.com/. Will @mui/joy be available anytime soon?

[siriwatknp]

@matthewkwong2 I can answer one of those.

Will @mui/joy be available anytime soon?

I would say no (if you mean the stable version). At this point, we have identify pain points that we have seen in @mui/material (mostly are about design & customization) and about to start the development. There are a lot of constraints to consider and we need to find a right balance which we will focus on them in Q4. Will keep you posted once we have a clear picture about the timeline.

I believe the default look of it will be similar to what we currently have in https://mui.com/

I'll let @danilo-leal (our designer) answer this question, but what I can tell is that it will definitely not look like material design 😂.

[oliviertassinari]

Open discussion for: Migrate the repositories mui-org/material-ui → mui/mui and mui-org/material-ui-x → mui/mui-x

For the official name. Could using mui/mui for this repository create confusion in the mind of our audience? I mean, if we have mui/mui-x and mui/mui-studio. What are people staring when they star mui/mui? The core components, or the company that provides a large set of tools? AFAIK (my assumption), the community prefers to star a piece of code, as close as possible to what they use. Why? Because stars are about leaving a social proof to others about the quality of something, as well as a bookmark. So maybe mui/mui-core would be better?

[oliviertassinari]

Almost all the tasks for the post-release of MUI v5 (including Material UI v5) have been done. I'm closing 🙏. Now, we can focus on v5 exclusively, unleash all the potential before even considering a v6 (2023?). Thank you all.