Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:23
From version 13.1
edited by Carlijn Kokkeler
on 2023/09/19 14:23
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/09/26 12:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -46,12 +46,8 @@
46 46  
47 47  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.
48 48  
49 -== 4. Assignment ==
49 +== 4. Key takeaways ==
50 50  
51 -Take a look at the release notes in the eMagiz Portal to ensure you know where to look.
52 -
53 -== 5. Key takeaways ==
54 -
55 55  * Keep as close to the latest buildnumber as possible for the entire environment
56 56  * The best option is to have the entire environment run on the same buildnumber
57 57  * A mix of buildnumbers in a runtime is not a good plan - conflicting behaviors may occur.
... ... @@ -58,10 +58,6 @@
58 58  * Read the release notes for builnumbers carefully to assess the impact - in case the impact is minimal proceed with the upgrade
59 59  * Make the buildnumber upgrades planable so the release schedule takes these actions into account.
60 60  
61 -== 6. Suggested Additional Readings ==
57 +== 5. Suggested Additional Readings ==
62 62  
63 -If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
64 -
65 -== 7. Silent demonstration video ==
66 -
67 -There is no video available as this is more a theoretical microlearning.)))((({{toc/}}))){{/container}}{{/container}}
59 +If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz)))((({{toc/}}))){{/container}}{{/container}}