Jerome2506
commented
4 years ago Seems for the explorer this was sometimes already done, but not consistently, hope this can return for upcoming versions: https://blog.ambrosus.com/dev-update-amberex-3-3-release-q1-2020-releases-35ba6a2c2fb https://blog.ambrosus.com/dev-update-amberex-3-2-5-release-a561c86f2257
The dev team is improving the various Ambrosus software on a daily basis, which we appreciate very much.
The issue at the moment is that we as node holders don't know what is implemented since nobody tells us. I'm personally in the lucky position that I can read code commits on Github and extract the information myself, but the average node owner/end user cannot and should not in my opinion. Also thinking about future clients that simply expect release notes for software in a business setting.
Moving forward I'd like to have small release notes pro-actively by the team that list these functional changes. This is valid for most Ambosus software but particular for NOP package, Hermes dashboard and Explorer (client facing software). It doesn't have to be a new Encyclopedia but something like this:
Example: "NOP Release notes 27-02-2020 - Implemented cron tasks for node auto-update. The NOP onboarding package now contains a daily cron-task that automatically updates the NOP package to the latest version. This ensures that your node is always running the latest version. You must manually upgrade your node to this version to benefit from this new feature. "
Example: "NOP Release notes 27-03-2020 - Upgraded mongoDB from 4.0.16 to version 4.2.1. The NOP package now contains an upgraded version of MongoDB for better security and stability."
Example: "Explorer Release notes 3.3.12 - Date selector range for Apollo has been improved - The Apollo page date selector has been improved in usability. Its now clear to the site user the date is an interactive field. Also a date range can be selected. Fixed minor issue with a date range not completely visible after selection since 3.3.11."
Suggestion from TestMCTest is to use the changelog.MD function from Github. But basically im open for any format. What could be something to consider is to post a link to it into telegram, medium and or twitter news channels. You are doing at great job improving the software, but you forget to tell others about it -> It is in a way also a marketing tool to show your software is actively maintained and growing..
I just learned that the suggestion has been accepted in Telegram and this task is created to follow its process on request of the community manager -> I think that's very good news and a good step towards more professionalism and maturity.
Further it was mentioned by the team they'd like to combine some tasks and deploy at once in a controlled release or versioning on certain days instead of deploying changes in a piecemeal way, This makes sense for the sake of stability and efficiency.