Indeed, versioning can be a maze of twisty little passages, all alike. From my tenure working on the Java platform, we were often shackled by multiple release trains, e.g. hotfix (security/escalations), maintenance, feature...
Minware has likely seen a sizable permutation of customer versioning strategies for releases, packages, APIs, lib…
Indeed, versioning can be a maze of twisty little passages, all alike. From my tenure working on the Java platform, we were often shackled by multiple release trains, e.g. hotfix (security/escalations), maintenance, feature...
Minware has likely seen a sizable permutation of customer versioning strategies for releases, packages, APIs, libraries and more. Would love to hear your thoughts on the pros/cons and best practices. It might even make a great topic for a future blog entry. ;)
Indeed, versioning can be a maze of twisty little passages, all alike. From my tenure working on the Java platform, we were often shackled by multiple release trains, e.g. hotfix (security/escalations), maintenance, feature...
Minware has likely seen a sizable permutation of customer versioning strategies for releases, packages, APIs, libraries and more. Would love to hear your thoughts on the pros/cons and best practices. It might even make a great topic for a future blog entry. ;)