Dear All,
does anyone from the active team still have access to the
npm credentials for uploading new packages? Its really not
acceptable how long this issue has been ongoing. There are
more than twohundred *listed* npm packages that depend of
thrift, possibly manyfold more unlisted.
Please upload a new package, or give someone access that
can to that.
All the best,
Mario Emmenlauer
On 23.04.20 11:34, Mario Emmenlauer wrote:
Hi all,
I've seen repeated requests for an update of the Node.js package,
see i.e. https://issues.apache.org/jira/browse/THRIFT-5039 and
https://issues.apache.org/jira/browse/THRIFT-5170.
I would be happy to understand if there is significant effort
involved to make a new Node.js release? The docs make it seem rather
trivial, but then again I've never done it. My reasoning is that if
the steps are sufficiently simple, the process could be added to
the build scripts, in the hope that more people can make more
releases in shorter time intervals.
Can someone help? Does that make sense or are there obstacles
I'm overlooking?
All the best,
Mario
