The meeting should make some decisions on the scope of the next release. Application of quality standards and features need also some discussion.
Rebasing of the old master to current develop is not possible since they diverge to much. As there are no tags on the master in gitea I would simply rename the old master to something like…
Next step is to define the next version number to be released. This needs to be done in a meeting with the main stakeholders of the project. In the meeting also the milestone bugfixes/features/impr…
Refactored the get_bool utility function and corrected for enabled button.
Pull request have been commented. Minor changes requested. Go ahaed if implemented.
Please remove commented code if not needed for backup solution implementation. In this case just remove.