Angular Material 1 will enter a maintenance mode
groups.google.com
Angular Material 1 will enter a maintenance mode
1–10 of 56 posts
Re: Angular Material 1 will enter a maintenance mode
#2this seems to be stardard practice at google. i've submitted tons of bugs ("issues") about app engine and compute engine, and google cloud in general, and after a month of them doing nothing, they respond with, "looks like we haven't done anything, closing"... they close it, you can't reopen. why fucking bother. just a bunch of idiots working over there padding their closed issue stats while they jerk off in larry's mouth.
Re: Angular Material 1 will enter a maintenance mode
#3I am the author of a slightly popular CSS library [1] and JS library [2] and I feel the pain explained here, trying to keep up the pace of issues and PR is daunting.
However, cmon Google! You are not a sole developer lost somewhere in Spain. Get your act together and really support your own libraries for a sensible amount of time. Or hire more people to do so.
Re: Angular Material 1 will enter a maintenance mode
#4The title is misleading, discussion linked has a clear explanation:
> You are correct that many valid issues/bugs have been closed without resolution.
> Our team simply does not have time to address all issues AND build Angular Material 2. (This is what we have consistently stated in our Forum posts).
> We welcome community leadership with Pull Requests. Often those PRs have side affects, their scope of changes is too large, and ultimately the risk is simply too great to merge.
> So we close/reject the PR... we do this to protect the existing user base. Pull Requests that have granular improvements and fixes are much easier to assess, test, and merge... and thus can be quickly merged.
> Pull Requests that are submitted referencing closed issues will then trigger us to reopen those issues; until the merge is complete.
> After Angular Material 2 has been released, we expect to continue to support and improve Angular Material 1 for many quarters.
> Both versions are important. Both are need to support the Angular 1 and Angular 2 developers
For me it's clear while the work on Material 1.x is not prioritized, it's not officially deprecated and PRs are still welcome if they are reasonable in size and impact.
Re: Angular Material 1 will enter a maintenance mode
#5The old joke about sleeping through the birth, life, and death of a JS framework is still alive and well I see.
Re: Angular Material 1 will enter a maintenance mode
#6Even though its deprecated, google did say Angular 1 was still supposed to be available as a fallback, and just closing issues and PRs is never correct, even if you are trying to phase it out.
Re: Angular Material 1 will enter a maintenance mode
#7The title is misleading, discussion linked has a clear explanation: > You are correct that many valid issues/bugs have been closed without resolution. > Our team simply does not have time to address all issues AND build Angular Material 2. (This is what we have consistently stated in our Forum posts). > We welcome community leadership with Pull Requests. Often those PRs have side affects, their scope of changes is to…
The fact that you felt that you needed seven lines of pull-quotes to repudiate the "misleading" title is a pretty good indicator that titles are, um, titles and thus cannot carry as much information as one might want. But even after reading the material you quoted, I don't see the title of this submission as inaccurate.
Re: Angular Material 1 will enter a maintenance mode
#8The title is misleading, discussion linked has a clear explanation: > You are correct that many valid issues/bugs have been closed without resolution. > Our team simply does not have time to address all issues AND build Angular Material 2. (This is what we have consistently stated in our Forum posts). > We welcome community leadership with Pull Requests. Often those PRs have side affects, their scope of changes is to…
The fact that you felt that you needed seven lines of pull-quotes to repudiate the "misleading" title is a pretty good indicator that titles are, um, titles and thus cannot carry as much information as one might want. But even after reading the material you quoted, I don't see the title of this submission as inaccurate.
I think removing the word "deprecated" would go a long way towards making the title less misleading.
Re: Angular Material 1 will enter a maintenance mode
#9I am the author of a slightly popular CSS library [1] and JS library [2] and I feel the pain explained here, trying to keep up the pace of issues and PR is daunting. However, cmon Google! You are not a sole developer lost somewhere in Spain. Get your act together and really support your own libraries for a sensible amount of time. Or hire more people to do so. [1] http://picnicss.com/ [2] http://umbrellajs.com/
support and google in the same sentence do not go well together
Re: Angular Material 1 will enter a maintenance mode
#10The title is misleading, discussion linked has a clear explanation: > You are correct that many valid issues/bugs have been closed without resolution. > Our team simply does not have time to address all issues AND build Angular Material 2. (This is what we have consistently stated in our Forum posts). > We welcome community leadership with Pull Requests. Often those PRs have side affects, their scope of changes is to…
The fact that you felt that you needed seven lines of pull-quotes to repudiate the "misleading" title is a pretty good indicator that titles are, um, titles and thus cannot carry as much information as one might want. But even after reading the material you quoted, I don't see the title of this submission as inaccurate.
Well, how about using the original title - "Surge Focus on Material 2"? It seems more appropriate as nothing in the discussion included a notice on deprecating the 1.x branch.