Documenting current practice here. We usually just increase the patch number at the moment. We increased minor or major version numbers in these cases:
- Release v4.4.0 No masters · openfoodfoundation/openfoodnetwork · GitHub Removal of master variants. Big irreversible database change.
- Release v4.3.0 · openfoodfoundation/openfoodnetwork · GitHub Rails 7.0
- Release v4.2.0 · openfoodfoundation/openfoodnetwork · GitHub Switching to Active Storage for images
- Release v4.1.0 Baklava · openfoodfoundation/openfoodnetwork · GitHub Split checkout preparation and session cookie changes
- Release v4.0.0 Pastel de Choclo · openfoodfoundation/openfoodnetwork · GitHub Switch to Puma
- Release v3.0.0 Spicy Meatball · openfoodfoundation/openfoodnetwork · GitHub Spree 2.1 and Rails 4.0
- Release v2.0.0 - Beta Carotene · openfoodfoundation/openfoodnetwork · GitHub Spree 2.0
So when we have a bigger change that is irreversible then we increase the minor version and if we need ofn-install to run provisioning first then we increment the major version. The version numbers are mainly indicating devops and instance managers if it requires action.