Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 5.1
edited by Erik Bakker
on 2022/10/14 13:52
Change comment: There is no comment for this version
To version 218.1
edited by Carlijn Kokkeler
on 2024/04/08 14:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get Ready
1 +218 - Sprightly Spring
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,13 @@
1 -Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
1 +In the last sprint cycle, we focused on releasing a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Please refer to our new [[runtime image>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Apart from this, we have improved event streaming logging, such that these logs are not cluttered with irrelevant information anymore. Moreover, we have removed the deprecated cloud option 'Root' from the portal.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]].
4 4  
5 5  =====New features=====
6 -* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
7 7  
7 +* Architecture: Several components are affected by the migration to Spring 6. Please check out the [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]] for specifications.
8 +* Architecture: Moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].
9 +
8 8  =====Minor changes=====
11 +* Manage - Monitoring: Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
12 +* Deploy - Cloud: Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
9 9  
10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 - ** Datagids, where there is now on hover action for example.
12 - ** Pop ups
13 - ** Context menus, also have on hover action
14 - ** Styling of scrollbars
15 -* Message Redelivery - admin logs improved to better analyze issues when they occur
16 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
17 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
18 -
19 -====Bug fixes====
20 -* Deploy - Deployment plan. Performance of page to deploy a release increases significantly
21 -* Store - Import resources was incorrectly done in specific cases, which is now fixed
22 -* Store - Target namespace will be imported when imported XML Message Definition
23 -* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus.
24 -* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.