Thanks to updates, you can use the latest technological possibilities in your daily activities. On your smartphone, Windows laptop… and in your logistics software solution. However, updating these systems always comes on top of your usual workload. Therefore, it makes sense this process must go as efficiently as possible. Without obstacles on the way. At PL Solutions, we share this opinion. That is one of the reasons why we recently introduced PL Solutions 3PL Dynamics Release Management. Now, it is up to you to claim your spot in this release process. Pick your moment to update. In that way, you will not face any surprises and we bring you to the newest version together.
In part one of this blog, we introduced PL Solutions’ new release policy: 3PL Dynamics Release Management. Do you want to learn more about the process towards this policy? Read it in part one here.
3PL Dynamics Release Management
Microsoft brings out a major release twice a year. Also known as version 19, version 20, etcetera. In addition, Microsoft also publishes two minor releases a year of those versions. Smaller updates. In PL Solutions’ release management, a distinction is made in the type of environment and number of updates. The main reason for this separation is the lead time needed to install the updates. You can imagine that for Microsoft SaaS and PL Solutions Cloud, almost all processes can be automated. That shortens the lead time big time. With an on-premise environment, it can take the developer up to multiple days to reach the server. For example due to portals that are not open (yet) or the speed of your servers.
Therefore, PL Solutions chooses to release one major release a year for on-premise customers. To publish two major releases for PL Solutions Cloud customers. And to update Microsoft SaaS customers monthly, including two major releases and two minor releases from Microsoft.
Developments in the future
Besides the new release policy, we as PL Solutions are working hard to provide customers with insights about the newest possibilities of the software after an update. Now, you can discover new functionalities in our blogs. Or via the training What’s New What’s Next. But we are finding out how to share release notes with you as a customer. However, we face some technical challenges here. Because how can we clearly communicate what changes our developers have made. Monthly, around 1500 code changes (commits) are made. That means that we will have to communicate around 10.000 commits when you update twice a year. Internally, we are busy finding ways to do so. We hope to share the first release notes in version 21 or 22 of Microsoft. In version 20, we will share release notes on main level.
Do you want to know more about 3PL Dynamics Release Management? Or do you have questions about sharing your operating hours and preferred day? Mail to firstname.lastname@example.org. Together we take the first steps towards a successful update process.
This article was written by Teun Slagter from our partner Boltrics