Hey all,
I am an Automation Engineer from Canada with ~1.5 years experience in VENUS 4 (and starting Venus 6 now).
Are there any automated routes to generate changelogs/patchlogs for the updating process? There’s some interest in tracking this and so far I’ve merely been commenting my changes in a comment section at the top of my methods. Crude, but effective.
However, others may want more detailed notes…
Any thoughts?
I’d recommend checking out some of the version control discussions on here with the search feature. I think git is possible with venus files but not line-by-line tracking, just generic commit hashes with comments. That might be what you need. What is the end user doing with this information?
As an example to what @Stefan mentioned, if you incorporate Git for version control across all your tools, you can also easily incorporate change logs and view them easily with trackable changes and perform recovery when needed.
You could also implement a CHANGELOG.md that automatically updates every time you make a commit.
Currently, I’m the end user. However others might re-visit some of my methods in future. I’d prefer to keep the system as fundamentally simple as possible with little to no time investment. Grouping code chunks in venus and commenting seems to be the least burdensome way of version control.
Could you give an example?
If you want to localize updating logs to VENUS, you could use the Read/Write functions for a CHANGELOG file that only runs given conditionals that you set.
Ah, seems I’ve sorted out my own solution actually!
Thanks for that screenshot yhs.allen!
