2024 Roadmap

[Mr0grog]

Nobody (including myself!) has done a lot of work here in the last year or so, but a couple recent issues, brought my attention back to this repo. When I first got added on as a maintainer, I made a laundry list of to-do issues, and never got half of them done. I’m currently dedicating some time this week and next week to try and get through them:

• Use promises and async/await instead of callbacks where applicable #84
• Add tests for actual metrics submission to Datadog #89
• Script versioning/publishing releases #91
• Support retries #108

Hopefully I’ll get a release out the door with all of those updates (and a few other assorted bits) before the end of the month.

There are some other, older issues that I’m not actively planning to work on. If you have a strong need for something not listed above, please comment and let me know! (PRs are always welcome, too.)

A few of these issues involve either breaking changes or require fairly complex code to support them (e.g. promises vs. callbacks). This library gets a lot of downloads on NPM, so I plan to continue deprecating-but-still-supporting the old stuff. However, that stuff eventually needs to be cleaned out, so I’m planning to fully remove most deprecated functionality in a major, breaking change in January 2025. (Maybe we’ll cut a 1.0!)

[Mr0grog]

v0.12.0 is now out and available.

There are now milestones for v0.12.1 (which I expect to ship before the end of 2024) and v0.13.0.

Once v0.13.0 has been live for a month or so, I expect to ship v1.0 (which should be early 2025). Despite some significant changes in v0.12.0, the overall architecture of this package has been pretty stable for years, and it’s honestly long overdue for a 1.0. The main reason I want to wait for v0.13.0 is that it includes removing our dependency on @datadog/datadog-api-cient. Instead, we can rely on Node.js’s built-in fetch implementation, but that requires updating the minimum Node.js version to v18, which is a significant breaking change.