-
-
Notifications
You must be signed in to change notification settings - Fork 946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versioning. Did version 3.2.16 changed? #2662
Comments
Yes as it was broken, I really didn't see this template revert as breaking as it's cloned and modified by end-users to fit their needs right? Do you regularly fetch the changes from this template? |
Lately yes as I am working on a moderately new project based on it, maybe too much? every month or so on average. |
Maybe next time should we create versions such as |
I'm unsure if I'm misremembering, but wasn't there a different 3.2.16 release?
I see the attempt to keep the core and the template repos on the same version but this has some drawbacks.
Changing public release versions is very confusing. It's more confusing than not having versions at all.
If the goal is to keep the version matching maybe it will be beneficial to add another digit like 3.2.16.2 for the template repo?
It's also hard to get fixes for bugs without getting major updates in the same version or commit (like getting the Admin working again without switching to a new Linux distribution). A quality-of-life change could be (if possible) to break the release (like 3.2.16.2 fixes 3.2.16.3 switch to Debian).
Thank you!
The text was updated successfully, but these errors were encountered: