You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
We've got a lot of different firmware versions, not necessarily built by our core team, but by other enthusiast as well.
It is easy to lose the overview, which firmware is based on which gluon-version.
Describe the solution you'd like
It would save me quite some time, if I could see which update paths are relevant for our community, by listing gluon versions similar to firmware versions in the statistics tab.
Describe alternatives you've considered
Another alternative would be to write a separate tool, that focuses on Firmware migration paths in detail. I hope that won't be necessary and that the overview of meshviewer suffices.
Additional context
Gluon allows for for an scm override, which affects the gluon version.
If used correctly, this allows for even finer control over the grouping of similar built firmwares.
But that's offtopic context, which just makes this request interesting for us.
The text was updated successfully, but these errors were encountered:
Hi,
to clarify this request:
this issue requests to have an additional group "gluon version" after Firmware Version in the statistics tab:
inbetween here after the firmware version.
This should show the string after the slash in the firmware field here:
So that one can also filter the gluon version, as some firmware versions have the same gluon commit.
If this is already possible to do it in the config, could you @xf- elaborate on that?
Is your feature request related to a problem? Please describe.
We've got a lot of different firmware versions, not necessarily built by our core team, but by other enthusiast as well.
It is easy to lose the overview, which firmware is based on which gluon-version.
Describe the solution you'd like
It would save me quite some time, if I could see which update paths are relevant for our community, by listing gluon versions similar to firmware versions in the statistics tab.
Describe alternatives you've considered
Another alternative would be to write a separate tool, that focuses on Firmware migration paths in detail. I hope that won't be necessary and that the overview of meshviewer suffices.
Additional context
Gluon allows for for an scm override, which affects the gluon version.
If used correctly, this allows for even finer control over the grouping of similar built firmwares.
But that's offtopic context, which just makes this request interesting for us.
The text was updated successfully, but these errors were encountered: