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
So, I would say exiftool is an endlessly developed project... I keep having new ideas and more improvements.
I don't think that the v0.5.x branch will be stable for some time, but currently it largely replicates the same features available in the 0.4.x branch with very few changes.
I would want to cutover to the 0.5.x branch before it really starts deviating in a crazy way. I certainly think I should stabilize the interfaces on the ExifToolHelper prior to making this cutover, but it may be months before I do away with the extraneous function calls over there.
When is it ever a good time to cut over to an incompatible upgrade? How do projects usually deal with that? I will certainly continue to support the 0.4.x legacy branch and will take PRs there, but certainly with all the Typing and linting that is happening, 0.5.x will look nothing like 0.4.x soon.
Also, how do projects deal with two different versions of documentation? 0.4.x and 0.5.x will not have compatible documentation
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So, I would say
exiftool
is an endlessly developed project... I keep having new ideas and more improvements.I don't think that the v0.5.x branch will be stable for some time, but currently it largely replicates the same features available in the 0.4.x branch with very few changes.
I would want to cutover to the 0.5.x branch before it really starts deviating in a crazy way. I certainly think I should stabilize the interfaces on the
ExifToolHelper
prior to making this cutover, but it may be months before I do away with the extraneous function calls over there.When is it ever a good time to cut over to an incompatible upgrade? How do projects usually deal with that? I will certainly continue to support the 0.4.x legacy branch and will take PRs there, but certainly with all the Typing and linting that is happening, 0.5.x will look nothing like 0.4.x soon.
Also, how do projects deal with two different versions of documentation? 0.4.x and 0.5.x will not have compatible documentation
Beta Was this translation helpful? Give feedback.
All reactions