Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 220.1
edited by Carlijn Kokkeler
on 2024/04/08 15:00
on 2024/04/08 15:00
Change comment:
There is no comment for this version
To version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
on 2023/08/29 11:07
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 -2 18-Sprightly Spring1 +204 - Found It - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,13 +1,18 @@ 1 -In the last sprint cycle, we focused on releasinga major version of our [[current runtime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]] baseimage for all our clientsrunningonthe [[currentruntime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.Pleasereferto ournew [[runtime image>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]and Spring 6 [[migrationpath>>doc:Main.eMagiz Support.MigrationPaths.migration-path-spring-6-migration.WebHome||target="blank"]]for moreinformation. Apart from this,we haveimproved eventstreaming logging, suchthat theselogs are not clutteredwith irrelevantinformation anymore. Moreover, we have removed the deprecated cloud option'Root'fromtheportal.1 +In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 18-Sprightly Spring||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.WebHome||target="blank"]]. 4 4 5 -===== Newfeatures=====5 +=====Minor changes===== 6 6 7 -* Architecture: Several components are affected by the migration to Spring 6. Please check out our [[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"]]. 7 +* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers. 9 9 10 -=====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 +====Bug fixes==== 13 13 11 +* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970) 12 +* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 13 +* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release. 14 +* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 15 + 16 +=====Infra and image changes===== 17 + 18 +* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.