Changes for page Impact of build number upgrade

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,0 @@
1		-Impact of builnumber upgrades

Parent

...	...	@@ -1,1 +1,0 @@
1		-WebHome

Content

...	...	@@ -1,4 +1,13 @@
1		-{{container}}{{container layoutStyle="columns"}}(((
	1	+{{html wiki="true"}}
	2	+<div class="ez-academy">
	3	+ <div class="ez-academy_body">
	4	+
	5	+<div class="doc">
	6	+
	7	+
	8	+
	9	+= Impact of builnumber upgrades =
	10	+
2	2	In this microlearning, we will focus on the helping you to assess the impact of upgrading to new buildnumbers.
3	3
4	4	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
...	...	@@ -17,6 +17,8 @@
17	17
18	18	eMagiz works hard to limit the number of buildnumbers. The general approach for buildnumber is that these are backwards compatible, so the impact of moving to the next buildnumber poses a minimal impact and risk.
19	19
	29	+
	30	+
20	20	== 3. Assessing the impact of changing buildnumbers ==
21	21
22	22	=== 3.1 Release notes & impact assessment ===
...	...	@@ -45,6 +45,8 @@
45	45
46	46	It is usually best to update the test and acceptance environment first and leave that running for a certain grace period. So that in case potential issues can be fixed still.
47	47
	59	+
	60	+
48	48	== 4. Assignment ==
49	49
50	50	Take a look at the release notes in the eMagiz Portal to ensure you know where to look.
...	...	@@ -57,6 +57,8 @@
57	57	* Read the release notes for builnumbers carefully to assess the impact - in case the impact is minimal proceed with the upgrade
58	58	* Make the buildnumber upgrades planable so the release schedule takes these actions into account.
59	59
	73	+
	74	+
60	60	== 6. Suggested Additional Readings ==
61	61
62	62	If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz