Saturday, June 1, 2024
HomeiOS Developmentconstruct - Dealing with Model Reverts in iOS Semantic Versioning and App...

construct – Dealing with Model Reverts in iOS Semantic Versioning and App Retailer Tips


I’m new to semantic versioning and have a query relating to iOS releases and App Retailer tips.

In keeping with Apple’s technotes, new model numbers should be added in ascending sequential order as you create new releases.

We use a model naming format of Main.Minor.Patch.

Suppose I launched a significant function (Model 2.5.0) that triggered points in manufacturing and must be reverted. Logically, I would want to decrement the main model to revert to the outdated state. For instance, downgrading from 2.5.0 to 1.5.1 would make conceptual sense however is just not supported by Apple’s tips.

The identical challenge arises with minor model reverts.

Given this case, how ought to I modify the model quantity if main or minor options have to be reverted?



Supply hyperlink

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments