this is not anything new with any framework. I think at some point you have to say I will go with v4.0 release it and then keep it that way until you see a benefit of moving to the next version. upgrade to the next version is not really required
On Monday, May 14, 2018 at 12:07:56 PM UTC-7, Skini wrote: > > I started development of a product with Angular 1.0, after some time > Google released Angular 2, so we had to write the client side code and > retest the entire product. > When Google released Angular 4 (there is no 3...), backward compatibility > was partial and again we had to re-write some portion of code, but retest > the entire applications. We found some bugs in the Angular 4 & reported the > same. Google has not fixed these bugs in 4 and has released Angular 5 along > with bugs reported in 4, but again lot of compatibility issues. Hence again > I have to resolve the compatibility issues and retest the entire > application. > > If it continuous like this, my product will never go live and I will spend > my entire life only in fixing the compatibility issues. I am not able to > understand what process/policy followed by Google for version upgrade. Why > they are not fixing the bugs in the same version ? Why the newer versions > are not backward compatible ? Why Google is not bothered about the pain of > application vendors ? > > If you look at Microsoft products, I have never faced this kind of issue. > > Did I make a mistake by choosing Angular ? > > -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
