Changes for page 241.1 - Wild West
Last modified by Erik Bakker on 2025/04/04 08:35
From version 186.1
edited by Carlijn Kokkeler
on 2024/01/15 14:47
on 2024/01/15 14:47
Change comment:
There is no comment for this version
To version 240.1
edited by Erik Bakker
on 2025/04/04 08:35
on 2025/04/04 08:35
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 2-FailoverFiesta1 +241.1 - Wild West - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,16 +1,10 @@ 1 -In the last sprint cycle, wefocused on ....1 +In this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. 4 - 5 -=====New features===== 6 - 7 -* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 8 - 9 -=====Minor changes===== 10 - 11 - 12 - 13 13 ====Bug fixes==== 14 14 5 +* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release. 6 +* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release. 15 15 8 +====Remarks==== 16 16 10 +* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.