Latest kibana requires nodejs 16, would it be possible to stabilize it? It's the latest LTS release. Thank you!
Makes sense to me given v16 has indeed been declared production-ready in late October, and I think I've seen williamh mention he plans to stabilise it soon too. Looking at the change log, I guess it should be safe to stabilise 16.13.0? We would have to wait for quite a while longer in order to be able to stabilise .1 but .0 both is the first LTS release of v16 and has been in the tree for 2.5 weeks now so the wait would be shorter. williamh: if you agree (I don't maintain net-libs/nodejs any more after all), go ahead and add CC-ARCHES to bug keywords when ready.
(In reply to Marek Szuba from comment #1) > Makes sense to me given v16 has indeed been declared production-ready in > late October, and I think I've seen williamh mention he plans to stabilise > it soon too. > > Looking at the change log, I guess it should be safe to stabilise 16.13.0? > We would have to wait for quite a while longer in order to be able to > stabilise .1 but .0 both is the first LTS release of v16 and has been in the > tree for 2.5 weeks now so the wait would be shorter. > > williamh: if you agree (I don't maintain net-libs/nodejs any more after > all), go ahead and add CC-ARCHES to bug keywords when ready. I'd go for 16.13.1, already using it with kibana and has a lot of changes compared to 16.13.0 (fixes, etc.).
(In reply to Tomáš Mózes from comment #2) > I'd go for 16.13.1, already using it with kibana and has a lot of changes > compared to 16.13.0 (fixes, etc.). In that case we'll probably have to delay this till January... But let us let the maintainer decide how to proceed with this.
Since this will be the first 16.x stabilized, we can stabilize the latest. Users that cannot upgrade will mask it either way and the others will probably want the latest.
Unable to check for sanity: > no match for package: =net-libs/nodejs-16.13.1
v16.14.2 is stable.
