Updated MTA roadmap and capabilities for 2026 @tknippenberg#11491
Updated MTA roadmap and capabilities for 2026 @tknippenberg#11491menditectadmin wants to merge 2 commits into
Conversation
|
Input from Menditect. For questions, please reach out to @tknippenberg |
|
m.travaille@menditect.com seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
|
||
| * The application model being tested must be stored in the Mendix Team Server repository. | ||
| * The MTA application and the application under test must be able to establish network connectivity with the Mendix platform APIs, including the Mendix Team Server and Project APIs. | ||
| * The application model being tested must be stored in the Mendix Team Server repository. In Q4 2026 MTA will start to become available for Airgapped deployments. This version allows for private Git or SVN repositories. |
There was a problem hiding this comment.
@tknippenberg, documentation should always reflect the current state of a product. As such, adding future plans is bad practice, and can pose issues if said plans fall through.
I recommend the following:
- Only keeping the changes to the release calendar.
- Discarding updates like "In Q4 2026 MTA will start to become available" and "Once Airgapped deployment is supported", and adding the actual content when air-gapped deployment is released.
There was a problem hiding this comment.
Agreed that the timeline doesn't fit on this page. But given that this is a page about a partner solution, I want to be a bit more lenient on fully limiting the contents to the current state.
What do you think about putting something in like:
Support for Airgapped deployments, to support private Git or SVN repositories, is currently on the roadmap
Then we tie the roadmap into this page, so we don't need to mention the timeline here, but we can illustrate that it's a topic where the partner is aware of.
|
That is Ok for me.
I get a lot of questions about this roadmap topic. If we can refer to the
release calendar that is fine. However, would it be possible to describe
somewhere which precise limitations we will solve with that update? That I
why I already added it to the documentation. I also understand your best
practice.
Kind regards,
Markus Travaille
Chief Vision Officer
***@***.*** ***@***.***>
Tel: +31854010494
Mob: +31619975135
Book an online meeting with me via
https://meetings.hubspot.com/markus-travaille
<https://meetings.hubspot.com/markus-travaille?uuid=4b8b920a-d0a4-4f2b-880b-9ac0f641adc1>
<https://www.menditect.com/>
*From:* NicoletaComan ***@***.***>
*Sent:* maandag 6 juli 2026 12:57
*To:* mendix/docs ***@***.***>
*Cc:* MarkusTravaille ***@***.***>; Author <
***@***.***>
*Subject:* Re: [mendix/docs] Updated MTA roadmap and capabilities for 2026
@tknippenberg (PR #11491)
***@***.**** requested changes on this pull request.
------------------------------
In content/en/docs/marketplace/partner-solutions/mta/_index.md
<#11491 (comment)>:
@@ -22,12 +22,12 @@ For more information about purchasing MTA, contact your Customer Success Manager
When purchased via Mendix, MTA can be used with any Mendix cloud
hosting option, with the below requirements:
-* The application model being tested must be stored in the Mendix
Team Server repository.
-* The MTA application and the application under test must be able to
establish network connectivity with the Mendix platform APIs,
including the Mendix Team Server and Project APIs.
+* The application model being tested must be stored in the Mendix
Team Server repository. In Q4 2026 MTA will start to become available
for Airgapped deployments. This version allows for private Git or SVN
repositories.
@tknippenberg <https://github.com/tknippenberg>, documentation should
always reflect the current state of a product. As such, adding future plans
is bad practice, and can pose issues if said plans fall through.
I recommend the following:
- Only keeping the changes to the release calendar.
- Discarding updates like "In Q4 2026 MTA will start to become
available" and "Once Airgapped deployment is supported", and adding the
actual content when air-gapped deployment is released.
—
Reply to this email directly, view it on GitHub
<#11491?email_source=notifications&email_token=AIT4ZKFU7R5TKBDJMPZ74BL5DOAYHA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTINRTGUYTMOJWG4Z2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#pullrequestreview-4635169673>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIT4ZKGDBLNIWWFJLBZXPOL5DOAYHAVCNFSNUABEKJSXA33TNF2G64TZHM3DQMJYHA2DOOB3JFZXG5LFHM2DQMJYGIZDSNRYG2QXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AIT4ZKG22WT62ZVZKYYX54T5DOAYHA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTINRTGUYTMOJWG4Z2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/AIT4ZKAKI6MINLDDMPMTAJ35DOAYHA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTINRTGUYTMOJWG4Z2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because you authored the thread.Message ID: <
***@***.***>
|
|
@tknippenberg, @menditectadmin, thanks for your input! You make very valid points. I will integrate the content in a way that does not outwardly indicate a timeline. |
|
I've added the following content:
Please let me know your thoughts. |
4 participants
No description provided.