v5.0.0-beta.1

[oliviertassinari]

I have updated the version of the private packages to a pinned: 5.0.0. The objective is so we can keep it the same going forward, avoiding diffs/noise in the release PRs. Private packages are never released, the version is useless from what I understand. We already use this tradeoff in the examples.

Important, a preview of how the header of the release looks and feels like:

---

---

As a side thought: We had 13 contributors in 10 days, the community has been quiet in the last few days. It seems that the pattern is older than this. We might want to spend more time on the issues and PRs, and less time on the ongoing initiatives. We were often at 20 contributors/week in the past, I was dedicating 80% of my time to issues and PRs, not initiatives. 80% was probably too much, I guess we need to find a balance and a reasonable target, it's a tension:

• too much time on issues & PRs mean we can't take on the boldest moves, innovate
• not enough time on issues & PRs mean we can't build the most loved UI components, leaving too many friction points behind, opening the door for competitors to catch up with what we do the best.

[mui-pr-bot]

No bundle size changes (experimental)

Generated by 🚫 dangerJS against 5708ded

[oliviertassinari]

@eps1lon Are you OK with the version change for the private packages? I wasn't too sure that it would be better, it seemed simpler though.

[eps1lon]

@oliviertassinari Did you run yarn release:version or did you manually update the versions?

[oliviertassinari]

@eps1lon I have used yarn release:version first, then did manual edits. For instance, reverting the version change to packages where only the test files changed.

[eps1lon]

Well you made a mistake when manually editing the versions since you forgot to bump @material-ui/codemod.

[oliviertassinari]

Thanks for raising. I think that I forgot to rerun the package version script after I rebased the branch to take in the changes between Monday and Wednesday.