It's time for tag v2.0.0!
amete opened this issue · comments
Given #149 is in, I believe it's time for a new tag, namely v2.0.0. We should also merge master into stable to keep everything in sync. Would you like to do the honors @graeme-a-stewart or should I go ahead? Let me know, many thanks.
Hi Serhan
I merged master into stable, so that is done. I am preping the tag now and working on release notes (that's the time consuming thing!).
So far I have this:
prmon v2.0.0 release
This is the Barnard's Star release
Average values for prmon JSON stats are now implemented as floats so that
the don't suffer from (bad) integer rounding.
Monitoring components now use a registry setup, allowing more reflection
in the code for components and, e.g., component specific help messages.
Thread counting now returns the total number of threads used in the
process tree, with nothing subtracted (previously 1 had been subtracted
as an assumed 'mother' thread).
Unittests have been updated to work in Python3, by default, with a new
CMake variable PYTHON_TEST if a different Python is needed, e.g. fallback
to Python2.
Hardware monitoring has been added, with prmon adding information about CPU,
GPU and memory resources found on the host to the JSON summary file under an
'HW' section. This can be disabled by adding the option '--suppress-hw-info'.
Prmon will report on the units used for each of the metrics if the option
'--units' is given (this is off by default). The information is added to the
JSON file in a 'Units' section, with sub-sections for 'Avg' and 'Max'.
Prmon now works properly on Arm Linux distributions.
Monitoring for NVIDA GPUs is added, with metrics on streaming multiprocessor
and memory use percentage, as well as memory and total number of GPUs used.
There are numerous improvements to the plotting script to add GPU metrics
and improve the handling of axes units.
Is there anything else I missed?
Looks like we've implemented a lot 😄 To me, this list looks fairly comprehensive.
It's possibly not super important, but we can also mention we improved the documentation (i.e. added code of conduct etc.) and improved the CI/CD environments (GitHub actions integration etc.).
Yep, I thought about those things, but they aren't really part of the software 'release' per-se, but more a rolling improvement to the documentation and background testing.
Maybe I add this at the bottom:
Additional improvements:
- The website documentation has been improved with a contribution guide and
code of conduct
- The CI system was improved, moving to GitHub Actions and updating the list of
platforms the CI runs against
Sounds good to me 👍
v2.0.0 tagged!