34
loading...
OpenNMS On the Horizon – Docs, Vue UI, Config API, JDK17, Time-Series, Docker, Kafka, Nephron, Catheter, Health Check, ReST
Since last time, we continued to work on documentation improvements and a new experimental Vue-based UI, plus the unified config API, JDK17 support, Time-Series API enhancements, Docker image improvements, Kafka CollectionSet enhancements, Nephron and Catheter, Health Check, and ReST query fixes.
diffutils to the Horizon Docker image.Thanks to the following contributors for committing changes since last OOH:
(Reposting from last OOH, in case you missed it.)
As this month shows, it turns out to be kind of a pain to come back from a holiday and immediately try to put out releases.
After looking at the calendar, where holidays lie, and what works best for fitting into sprints, we have decided to move the release day forward.
The new release schedule is: second Wednesday of the month.
This means the July releases move foward to Wednesday, July 14th.
OpenNMS is on a monthly release schedule, with releases happening on the second Wednesday of the month.
The next OpenNMS release day is July 14th, 2021.
We currently expect a Horizon 28.0.1 release, plus updates for all supported Meridian releases.
The next major Horizon release will be Horizon 29.
The current roadmap for Horizon 29 includes the following goals:
With Meridian 2021 recently out, we do not yet have a specific timeline for Meridian 2022.
Expect it to include -- at the very least -- the JDK11 requirement and flow aggregation improvements from Horizon 28.
Ideally it will contain work going into Horizons 29 (and probably 30) if our timeline holds.
Ideally it will contain work going into Horizons 29 (and probably 30) if our timeline holds.
Note that this is just based on current plans; dates, features, and releases can change or slip depending on how development goes.
The statements contained herein may contain certain forward-looking statements relating to The OpenNMS Group that are based on the beliefs of the Group’s management as well as assumptions made by and information currently available to the Group’s management. These forward-looking statements are, by their nature, subject to significant risks and uncertainties.
...We apologize for the excessive disclaimers. Those responsible have been sacked.
Mynd you, møøse bites Kan be pretti nasti...
We apologise again for the fault in the disclaimers. Those responsible for sacking the people who have just been sacked have been sacked.
If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.
34