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
A surprising number of places in the application believe a product version number is strictly of the form X.Y, including assumptions such as Y can only be a single digit, Y can only be 0 (seriously?), and a version can be freely converted to a number for no good reason I can think of.
We have an internal need to stand up a doc set with a minor version number of the form X.Y-Z, even if we never release it that way externally. I expect this to be a recurring requirement.
I could just surrender to the potentially inevitable and label it "MarkLogic 42", but I'm first going to make a good faith effort to actually expand the app's narrow minded notion of what a version looks like.
The text was updated successfully, but these errors were encountered:
A surprising number of places in the application believe a product version number is strictly of the form X.Y, including assumptions such as Y can only be a single digit, Y can only be 0 (seriously?), and a version can be freely converted to a number for no good reason I can think of.
We have an internal need to stand up a doc set with a minor version number of the form X.Y-Z, even if we never release it that way externally. I expect this to be a recurring requirement.
I could just surrender to the potentially inevitable and label it "MarkLogic 42", but I'm first going to make a good faith effort to actually expand the app's narrow minded notion of what a version looks like.
The text was updated successfully, but these errors were encountered: