3.0 Official Release #3637
|
@igaw What's the outlook for a nvme cli 3.0 official release? I have a few users that are reluctant to load a beta release asking when the official release will be available. |
Replies: 2 comments 1 reply
|
Maybe some background first. The initial plan for 3.0 was to refactor and clean up the existing code base, addressing the technical debt from libnvme 1.x. After the 3.0 release, I wanted to look into bringing the fabrics connect logic into the modern era. After the PoC on the fabrics code showed that we needed to update/modify many of the fabrics-related APIs, it quickly became clear that it would probably be a good idea to continue working on the fabrics orchestration features before the 3.0 release. We have made very good progress, and I would say the technical debt cleanup is mostly done at the API level (there is still some internal work left, but we can deal with that later). For the fabrics orchestration features, we have all the necessary building blocks integrated, and work on the final piece (nvme-discoverd) has started. For 3.0, nvme-discoverd is not crucial, and I am considering whether we should enable it by default for the 3.0 release anyway, or whether we should give ourselves some slack and more time to stabilize it. So, in short, we are entering the stabilization phase for 3.0. This means bug fixing and testing, while continuing some progress on nvme-discoverd. However, nvme-discoverd is not really a release blocker. We have already received some typical regression bug reports, and I expect more over the next few weeks. The plan is to cut the first release candidate soon and then see how the feedback looks. If things calm down relatively quickly, I think we could see a release in August. This means that anyone who has time to test the current code base can help a lot in getting the release out earlier. Positive feedback is also important to me. So, if you can confirm that everything looks fine for the SanDisk/WDC plugin and that nothing is seriously broken, that would be a great help. |
|
Thanks for the background and feedback @igaw. I haven't noticed any new issues with either the Sandisk or WDC plugins. This week is a short week for me but I will try to do some more extensive testing of both plugins on the latest 3.0 beta release next week. |
|
I've updated the milestone planing, so we have a clue where we are. I've set the release date to August 28, 2026 though after updating the list, it's going to be a lot of work. https://github.com/linux-nvme/nvme-cli/milestone/6 |
Maybe some background first. The initial plan for 3.0 was to refactor and clean up the existing code base, addressing the technical debt from libnvme 1.x. After the 3.0 release, I wanted to look into bringing the fabrics connect logic into the modern era.
After the PoC on the fabrics code showed that we needed to update/modify many of the fabrics-related APIs, it quickly became clear that it would probably be a good idea to continue working on the fabrics orchestration features before the 3.0 release.
We have made very good progress, and I would say the technical debt cleanup is mostly done at the API level (there is still some internal work left, but we can deal with that later). For the…