On 19-11-29 03 h 08, László Böszörményi (GCS) wrote: > 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? > > [3] https://www.convective.com/angularjs-end-of-life/
I wasn't aware of this and although I am not sure you should base your decision solely on my point of view (I don't have tons of experience maintaining things in Debian), here's what I think. 1. If it's not too much work, you should package 1.7.x, not worry too much about breakage and add something like "(Breaks: libjs-angularjs (<< 1.6.0)". If you don't have the energy, I think leaving this package as-is is also fine. 2. I don't think this package should be removed from unstable before the end of the LTS period, as it's still useful and will ease the transition to Angular (if it's packaged). 3. An RC bug about AngularJS being EOL should be opened to make sure libjs-angularjs doesn't migrate to testing and be released in Bullseye. 4. You should contact the security team // the release team and see what they think of this. Do you have any plans to package Angular? I think putting your energy there would be a much wiser move than on a package bound not to be released in Bullseye. Thanks for your work on this package! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
signature.asc
Description: OpenPGP digital signature
