Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 180.1
edited by Carlijn Kokkeler
on 2023/10/12 14:08
Change comment: There is no comment for this version
To version 184.1
edited by Carlijn Kokkeler
on 2023/10/12 16:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,13 +5,15 @@
5 5  **Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 6  
7 7  == **Release Date Change** ==
8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (3:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
8 +As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
9 9  
10 10  == **Deployment Plan** ==
11 11  
12 12  //__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is now stopped first, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
13 +The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
14 14  
15 +{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
16 +
15 15  //__Editing release properties__//
16 16  With this release, it will be possible to change the description of a property by editing the property.
17 17  
... ... @@ -56,7 +56,7 @@
56 56  All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
57 57  
58 58  //__Update flow designer version__//
59 -The framework used in the flow designer has been updated to the latest version.
61 +The framework used in the flow designer has been updated, improving performance.
60 60  
61 61  //__Carwash track TLS versions in logging__//
62 62  A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
... ... @@ -79,8 +79,6 @@
79 79  //__Alphabetical sorting on user level in HTTP statistics__//
80 80  Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
81 81  
82 -//__SOAP Web services path__//
83 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
84 84  
85 85  == **Bug Fixes** ==
86 86