Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 157.1
edited by Carlijn Kokkeler
on 2023/11/21 12:27
Change comment: There is no comment for this version
To version 256.1
edited by Carlijn Kokkeler
on 2024/06/03 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +222 - Flee Frustration
Content
... ... @@ -1,19 +1,10 @@
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.
1 +In the last sprint cycle, we done several improvements for the Design and Deploy phases. Moreover, we have improved the Event Catalog overview for Catalog users. Our bug fixes concern the import of xsds, the deletion behaviour of containerse, and the generation of scope properties.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]].
4 4  
5 -=====New features=====
5 +====New features====
6 6  
7 -* 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.
8 8  
9 -=====Minor changes=====
10 10  
11 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
12 -
13 -
14 14  ====Bug fixes====
15 -
16 -
17 -
18 -
19 -
10 +* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.