Hi, On Tue, Nov 26, 2019 at 10:18 PM Louis-Philippe Véronneau <[email protected]> wrote: > On Tue, 4 Apr 2017 11:40:27 -0400 Jeffrey Cliff > <[email protected]> wrote: > > Upstream has released a couple of new versions, currently at 1.6.4 > > https://github.com/angular/angular.js/releases > > Angular JS has had multiple releases since the 1.6.1. version packaged > in experimental, including a major version release (1.7). > > Would it be possible to update it to the latest current version (1.7.9)? Indeed, I'm lagging with its maintenance. Part of me was afraid what would be the best way to maintain AngularJS. Its releases are not incremental, but contains breaking changes. See for example the 1.5 -> 1.6 [1] or the 1.6 -> 1.7 [2] migration guide and their 'breaking changes' parts.
> If you don't have time to do this, would you be ready to accept an NMU > doing this? I plan to do it finally on the upcoming weekend. However I ask for guidance how the package should be handled. If you follow the development of AngularJS then you know its end of life [3] since July 1, 2018 (more than a year ago). Its still supported with critical updates including security fixes until June 30, 2021. Indeed, that's about one and half years from now, but see the current situation. With the package update developers will need to update their web applications to support the (breaking) changes in AngularJS 1.7.x just to realize its end-of-life status. Maybe they already started migrating to an other web framework or better start migrating now to an other one. Does it worth to update the package or should it be removed from our archives? Regards, Laszlo/GCS [1] https://docs.angularjs.org/guide/migration#migrating-from-1-5-to-1-6 [2] https://docs.angularjs.org/guide/migration#migrating-from-1-6-to-1-7 [3] https://www.convective.com/angularjs-end-of-life/
