[docs] Bite the bullet and go for v1-beta #9706
Conversation
README.md
Outdated
| > Should I start with v1-beta? But beta is a beta, so it's not a final product and I'm not guaranteed anything. | ||
|
|
||
| People are starting projects with v0.x which given the quality and stability of v1 they shouldn't be. The v1-beta effort started in May 2016. | ||
| There are lots of us using v1-beta in production already with no problems and the odd breaking change is less hassle than upgrading from v0.x to v1-beta. |
There was a problem hiding this comment.
I'd suggest changing:
There are lots of us using v1-beta in production already with no problems and the odd breaking change is less hassle than upgrading from v0.x to v1-beta.
To:
Many of us are already using v1-beta in production with no problems and resolving the occasional breaking change is less of a hassle than upgrading from v0.x to v1-beta.
There was a problem hiding this comment.
"Less hassle" is also gramatically correct - and less words. 😄 I agree with the rest of your suggestion.
README.md
Outdated
| > Should I start with v1-beta? But beta is a beta, so it's not a final product and I'm not guaranteed anything. | ||
|
|
||
| People are starting projects with v0.x which given the quality and stability of v1 they shouldn't be. The v1-beta effort started in May 2016. | ||
| There are lots of us using v1-beta in production already with no problems and the odd breaking change is less hassle than upgrading from v0.x to v1-beta. |
There was a problem hiding this comment.
"Less hassle" is also gramatically correct - and less words. 😄 I agree with the rest of your suggestion.
README.md
Outdated
|
|
||
| Yes, you should. We often get this question: | ||
|
|
||
| > Should I start with v1-beta? But beta is a beta, so it's not a final product and I'm not guaranteed anything. |
README.md
Outdated
|
|
||
| > Should I start with v1-beta? But beta is a beta, so it's not a final product and I'm not guaranteed anything. | ||
|
|
||
| People are starting projects with v0.x which given the quality and stability of v1 they shouldn't be. The v1-beta effort started in May 2016. |
README.md
Outdated
|
|
||
| People are starting projects with v0.x which given the quality and stability of v1 they shouldn't be. The v1-beta effort started in May 2016. | ||
| There are lots of us using v1-beta in production already with no problems and the odd breaking change is less hassle than upgrading from v0.x to v1-beta. | ||
| They are just creating extra work for themselves as they will have to transition at some point. |
There was a problem hiding this comment.
This sentence needs to go before "There are lots of us" (or the @kgregory's suggested change.
README.md
Outdated
| There are lots of us using v1-beta in production already with no problems and the odd breaking change is less hassle than upgrading from v0.x to v1-beta. | ||
| They are just creating extra work for themselves as they will have to transition at some point. | ||
|
|
||
| Material-UI will never be a final product, you will never be guaranteed anything neither with v0.x nor v1, v2, etc. |
There was a problem hiding this comment.
"whether with v0.x, v1, or an future release."
There was a problem hiding this comment.
Really?! Wow, I didn't know an future was English.
There was a problem hiding this comment.
That's a new one for me as well.
There was a problem hiding this comment.
Bah, "any", sorry. Typos in suggested changes are not good! 😦
There was a problem hiding this comment.
@mbrookes Do you mind directly committing on v1-beta? :)
oliviertassinari
force-pushed
the
readme-use-v1-beta-over-master
branch
from
b956b6c to
8ec94b5
Compare
|
@oliviertassinari @kgregory @mbrookes - should we add a warning to http://www.material-ui.com/#/get-started pages so we make sure anyone looking at the project for the first time is pointed towards the beta? |
cc @eyn, @mbrookes, @kgregory