first v4 alpha version

[dtassone]

No description provided.

[dtassone]

Packages are not published yet

[oliviertassinari]

Noise?

[oliviertassinari]

Also, I wonder, would it be better to have a single changelog at the root developers can browse? Instead of having to read a dozen of changelogs when they want to update (in the longer term, once we have more packages?

[dtassone]

Yes I was trying lerna version

[oliviertassinari]

Should we rename the branch release -> docs?

For context, in the main repo, we use a different repository to have versioning support of the docs, but that's for another day 😁.

[dtassone]

Should we rename the branch release -> docs?

I think release makes more sense in the industry

[dtassone]

For context, in the main repo, we use a different repository to have versioning support of the docs, but that's for another day 😁.

Why?? it sounds overcomplicated 😄

Maybe we should review the process after this release

[oliviertassinari]

I think release makes more sense in the industry

I was wondering because we push releases on the master branch which could be confusing with another branch of the same name. The current use case for the release branch is to deploy the documentation. On the main repository. We frequently add commits on the docs branch that aren't released, only so we can update the documentation.

[dtassone]

I think release makes more sense in the industry

I was wondering because we push releases on the master branch which could be confusing with another branch of the same name. The current use case for the release branch is to deploy the documentation. On the main repository. We frequently add commits on the docs branch that aren't released, only so we can update the documentation.

Maybe we should change the netlify config so docs point to the release branch and not the docs branch ?

[oliviertassinari]

Why?

I think that it started with the requirement to version the documentation https://material-ui.com/versions/, then we double down on using it to not create noise for synching the translations of the documentation. cc @mbrookes.

[dtassone]

Why?

I think that it started with the requirement to version the documentation https://material-ui.com/versions/, then we double down on using it to not create noise for synching the translations of the documentation. cc @mbrookes.

Ahh yes the translations, I remember the conversation now :)

[oliviertassinari]

Ahh yes the translations, I remember the conversation now :)

We are experimenting with moving the translation to "source" repo. Crowdin has made a chance that reduces noise that seems to make it sustainable. So I guess the only reason for a different docs repository will be versioning, but not sure, hope Matt can 💡 the situation :)