-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Are you alive? #788
Comments
You right guys, We cant wait anymore, as @vamsivarikuti said, You said we can start using Material2, but you are not pro like ASP.NET Teams, they communicate with devs via conf and standups. |
Hey guys, can you think carefully before writing such messages? Do you think Google people are actually robotos which can sit and build you components for 24/7? or do you think they just sitting on a beach drinking cocktails ? They work very hard for you to get for free high quality products. Does it say anywhere this project is ready for production? Presentations were just for preview what current progress is. No one ever said go and use it in production. Stop such annoying behavior and these all questions "when"? (and questions "are you really Google?") Be respectful! If you don't like something go and help to build it, otherwise just go and use whatever else is there. They don't have to deliver anything for you by tomorrow. Be patient! |
Yeah! On their place I would go mad in a few days if I should constantly close endless duplicate issues after people not used to search and not able to wait. |
@m0t0r you right, but one thing, They work very hard not just for us to get what you call free high quality products. They create Angular and Materials for google's products in first place. So thanx to the community too, they are also working by delivering Feedbacks and some PRs. |
@m0t0r I agree with all you said, but I also understand the frustration of lack of communication. This project have very high expectations but no roadmap, no feedback, no documentation and low activity (specially in the last weeks). Also, some weeks ago the Angular Material team announced that they will focus intensively on Angular Material2 on Q3. So, I guess that many people has taken decisions and bet on this project based on that announcement and all this situation is frustrating. I don't want to be annoying or no respectful, but I think that better communication will help more people to contribute on this great project. |
Released alpha.5-3 this morning, which is exactly what alpha.6 will be except for using Delays on releasing alpha.6 have been due work that's not directly "make new components". If you look at commits and PRs, you'll still see a steady stream of going-ons. Nothing should be blocking moving to Angular rc3 other than some peer dependency warnings (which AFAIK can be ignored). Most of my time recently has been trying to get material2 working with Angular's offline compiler, which is exposing bugs in the tooling that need to be resolved. The whole process is somewhat time consuming, but is necessary to validate this tooling so that Angular 2 itself can get to final. Important, but not very visible. If you have been following Angular, you might know that Kara has been driving the new Other things include:
|
@jelbourn @kara are you still working on this project?
Many developers are using material2 and now we are blocked because we can't upgrade to RC3 since alpha-6 is frozen. Could you please make some communication about what is happening and please let us help you by detailing the roadmap.
@jelbour @kara are you really Google?
The text was updated successfully, but these errors were encountered: