Add guidance on feature rollouts and Mendix version upgrades to OTA updates doc - #11839
Open
jdiehl wants to merge 5 commits into
Open
Add guidance on feature rollouts and Mendix version upgrades to OTA updates doc#11839jdiehl wants to merge 5 commits into
jdiehl wants to merge 5 commits into
Conversation
…rify OTA vs version upgrade limitations, reorder sections
…app for existing users
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two new sections to the "Updating Native Apps" (OTA) page, explaining
two release strategies not previously documented: rolling out features that
require a full app store release, and upgrading the Mendix version safely.
Applied to refguide (Studio Pro 11), refguide10, and refguide9.
Changes
explains how to use OTA to prepare a feature while keeping it hidden
behind a constant (via a nanoflow decision or conditional visibility),
then enable it with a small, low-risk app store release. Keeps old and
new app versions compatible while the release is under Apple review.
upgrades separate from feature work, keeping model changes minimal, and
explains that a compatible model lets the old and new native client both
work against the upgraded runtime, so the new client can ship via a
normal app store release without OTA.
Updates" and before "Enabling and Building an App with Mendix OTA
Updates Enabled," keeping strategy guidance grouped with the existing
use-case guidance.