General Note for all #contest-dashboard members: For all those discussing about the Node-Red Contesting Dashboard, please add #contest-dashboard to the subject line of any new topic so the messages get tagged for later reference.
Hi John,
To start we are still finalizing the official release version of the Node-Red-Contesting-Dashboard. Sorry for any confusion that might have occurred in publishing early.? We had some major errors that cause node-red to crash and reverted to the previous issues.? Those got resolved and are going to be push shortly.?
The update structure will look like this. The package.json is getting version updates in the file to current status. (This is used via standard NPM packages and Node-Red Modules) The structure will be the following:
v<major>.<minor>.<patches>
major - Changes that are major requirement that breaks the current implementation of the dashboard. Might require reinstalling via Node-Red Script.
minor - Most Features that are implemented will be here.
patch - Commits that are bug fixes and tweaks.
The version will be visible on the Dashboard Upgrade Section of the Config tab in the dashboard.? The current value is what is on your local machine, while the latest value uses Github to determine the latest version.
Note there will be 2 release tracks for the dashboard. Each of these are in different git branches, allowing the ability to switch easily. They also change what version is the latest.
1. Traditional
Most Users will be recommended to use this.
Will be tested more thoroughly than option #2
2. Rolling.
This will be our development branch.
Note this may have large bugs, varying changes quickly, ...
Knowing how to use Node-Red and Git is helpful in using this branch .
Let me know if you have any questions.
73,
Connor KD9LSV
Connor KD9LSV