--- title: "Release Notes" canonical: "https://help.callroute.com/space/CKB/698777623/Release%20Notes" format: markdown --- ## Release Management We operate a continuous improvement release cycle so that you can benefit from improvements we make to the platform as quickly as possible. Traditional release cycles follow a quarterly or bi-annually release cadence where bug fixes and feature improvements are bundled into a single service pack and released at the end of the release cycle. Whilst this can generate some excitement when service packs are released packed full of new features and improvements, you have to wait an extended period of time for them. Where you are experiencing a bug or inefficiency, that may have been fixed early in the release cycle, but you’re not able to benefit from that fix until the service pack is released at the end of the cycle. This means you may have to wait months before your problem has been resolved. With a continuous release cycle we aim to reduce this wait time for features or fixes to issues that may arise from time to time by releasing updates as soon as they have passed through quality assurance. We do try to limit the frequency of change as much as possible. Therefore we release updates once every 2 weeks. This ensures that you get the best experience possible as fast as possible and it also ensures that we bring performance and stability improvements into the platform for all our benefits. This does mean that some of the releases we perform are not very exciting with new big features until the final components are released that enables us to turn on the feature for you. As Callroute is a multi-tenant platform, releases affect every customer and are not limited to a per customer release. Therefore, we cannot provide a release cycle or maintenance window that is targeted specifically to you. ### Maintenance Window Unless there is an emergency change, all releases are performed during our weekly maintenance window. This is currently: **Every Tuesday between 9am at 11pm GMT/BST** Whilst the window is broad we assess the impact of the change and whether the release could be service impacting or require our portal to enter maintenance mode. A lot of our releases are transparent and require no maintenance mode. They can be implemented alongside current production services and then switched over in a single ping meaning no loss of service and the change is not seen or felt by you. These non-service impacting changes are made between the hours of 9am and 5pm GMT/BST. For changes that could potentially be service impacting and require portal downtime, these changes are applied between the hours of 8pm and 11pm GMT/BST as the system is not heavily used during these hours. Although we have a weekly maintenance window does not necessarily mean that we will use it on a given week. Some weeks we have no releases and therefore the window is forfeited until the following week. ### Emergency Maintenance From time to time there are changes that need to be hotfixed into production because there is a serious issue with the platform that is degrading our service offering to you. When this occurs we reserve the right to release hotfixes into production outside of our regular maintenance window. These can happen at any time. However, we will assess the impact in order to deploy at the best convenient time. Where such maintenance is required and poses a risk to our calling service or our web platform requiring maintenance mode, you will be sent an email notifying you when this will be happening and the services potentially impacted. ### Customer Release Notifications Where releases pose a risk to the overall calling service or access to the web portal is restricted you will be notified by email at least 24 hours prior to the release informing you. If releases pose no calling outage risk or the release does not require maintenance mode, you will not be proactively notified and instead you should monitor this release notes section that will contain updates once released. ### Early Warning Of Changes We are aware that you might want early warning of changes coming to the portal and service. You can stay up to date with what we are working on at any time using our public roadmap [https://callroute.com/roadmap](https://callroute.com/roadmap) This shows the features that we are working on actively and what we have planned along with an estimated date for release. ![image-20240226-223426.png](media://659a304d-b5b5-460c-b2c3-f6e310f42498) You can also submit a feature request directly to the product team if you have identified an area of improvement that will make your admin life easier. Additionally, you can keep visiting this section of our knowledge base for regular updates on features released. Each month we create a new page and we will update it with features released in each cycle during the month. Typically you will notice at least 2 updates per page per month. So please keep checking. In terms of providing more detailed information of what to expect such as UI/UX changes, these are hard for us to proactively prepare you for. This is because with the continuous release cycle the UI is the last component to be implemented before a feature release. In simple terms, the UI/UX experience may not be demonstrable until the day before, or in some cases hours before release. We will look to improve our communicaton with you on releases but we would much rather you benefit quicker from our hard work and notify you after, than withhold the release whilst we prepare marketing and informational content and send that out to you before implementing. However, a lot can be learned from following these steps: 1. Check our [roadmap](https://callroute.com/roadmap) every week 2. Check our [release notes](https://help.callroute.com/space/CKB/698777623/Release+Notes) twice a month 3. Subscribing to our [Youtube channel](https://www.youtube.com/@callroute2793) for feature update briefings 4. Following our [LinkedIn company page](https://www.linkedin.com/company/callroute) Below you can find details of our release notes. > Macro (pagetree)