Approach to version control
Posted: Sun Feb 10, 2019 1:26 pm
I was pleased to see the LibreDrive feature enable itself today on my Asus drive and want to thank/acknowledge the continued development on makemkv.
However, having functionality install itself via a back door without user consent raises certain issues? E.g. what happens if an update breaks something? If updates are tied to official releases then from a user perspective it becomes straightforward as the user manages which version is installed and can back-date if necessary. Feels like we have moved beyond automatic key download and we are now in a new place in terms of update management/consent. Deploying updates without installing a new version has the potential to be very convenient, but does anyone else think this raises some points to consider for how versioning is managed in the future?
However, having functionality install itself via a back door without user consent raises certain issues? E.g. what happens if an update breaks something? If updates are tied to official releases then from a user perspective it becomes straightforward as the user manages which version is installed and can back-date if necessary. Feels like we have moved beyond automatic key download and we are now in a new place in terms of update management/consent. Deploying updates without installing a new version has the potential to be very convenient, but does anyone else think this raises some points to consider for how versioning is managed in the future?