Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
on 2023/08/15 12:23
Change comment:
There is no comment for this version
To version 158.1
edited by Carlijn Kokkeler
on 2023/11/21 12:42
on 2023/11/21 12:42
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 -20 3-FastPaced1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,19 +1,31 @@ 1 -In the last sprint cycle, we focused on the s calability andstabilityofour infrastructure. On top of that, we willreleaseseveralminor changeswitha potentially significantimpact.1 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.20 3-FastPaced.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]]. 4 4 5 +=====New features===== 6 + 7 +* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. 8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 9 +* All - The next generation architecture is the default now. New models will use this generation as default. 10 + 11 + 12 + 5 5 =====Minor changes===== 6 6 7 -* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023) 8 -* Manage - Alerting: Identifiers of triggers are now visible in the edit screen. 15 +* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 16 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 17 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. 9 9 19 + 20 + 10 10 ====Bug fixes==== 11 11 12 -* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016) 13 -* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597) 14 -* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release. 23 +====Infra and image changes==== 15 15 16 - =====Infraandimage changes=====25 +* Infra: New logging feature enabling us to make better choices in encryption standards. 17 17 18 -* Infrastructure: Tightened security policies for a more secure infrastructure. 19 -* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower 27 + 28 + 29 + 30 + 31 +