This guide runs through a summary of how the ezyVet team update your site and the update process.

Technology is always changing and advancing, and to stay on the cutting edge we need to ensure we are running consistent and timely updates to the ezyVet system.
This includes updates for security purposes, updates for new features, fixes for issues in the system and updates that will make the system more robust.

ezyVet's update process follows an 'agile' structure  - this is a common structure software companies use.
This means that our updates follow a regular, repeatable work cycle.
New features/improvements that are to be included in the next update are compiled, reviewed and documented in our ezyVet updates and release notes before the update to the latest version is actioned.

We update our customers sites in stages - this means that we cycle through a structured list of customers, where we update sites in batches.

Customer sites are grouped into the below, distinct groups. These groups define which stage in our update cycle your site will be upgraded.

Version adoption groupWho can be grouped here?
Master Version (ALPHA)We do not have any customers on this version. This version is primarily for development and testing of the new features and improvements to be included in the next release. This is the ALPHA version of ezyVet where the latest and greatest code is written. Only our demo sites, testing sites and corporate head office central sites are to be on this version.

Sites in the go-live and implementation process will start in this version and will gradually move down to the stable versions during the update roll out.

We will not move any clients into this version regardless of request.
Bleeding Edge Version (BETA/ BE)We have a very small group of customers who are on this release type. This version of ezyVet is where the Master version code is merged down into.

This means the Bleeding Edge (BETA/BE) customers are the first to get any new features and updates, however, they are also applicable to the potential instability that come with changes to the code and new features.

BE is where we are effectively seeing the updated code being used in a true, customer facing context so any coding aspects that are not working as intended or are not functional at a clinical level are caught through feedback from our BE customers, fed back to our technical team and resolved before the next release cycle.

If your clinic has more than 19 users, you cannot be on this version type.
*Stable - Early AdoptionOnce the updated code has been available in the BE customers sites for a set period of time and the feedback has been positive, we will then release this code by updating customers in the Stable - Early Adoption group. This means they are the first 'batch' of sites to receive the new update.

If your clinic has more than 75 users, you cannot be on this version type.
*Stable (Normal Roll Out)Once the updated code has been available in the Stable - Early Adoption customers sites for a set period of time and the feedback has been positive, we will then release this code by updating customers in the Stable (Normal Roll Out) group. This means they are the next 'batch' of sites to receive the new update. This is where the bulk of our customers sit in the update cycle and this is the most stable version of ezyVet.
*Stable - Slow ReleaseA small number of customers are in this group. This group is reserved for customers with large sites and 24/7 clinics, where the update could have direct impact on their site. For these clinics, the team will often need to organize an agreed upon time for update to avoid any disruption to their day to day workflow.

If your clinic has more than 200 users in the system, you must remain on this version type.

*Stable is the most robust and reliable version of ezyVet. 

As a customer, you can request to be moved into the different categories for the stable releases if you meet the criteria as listed in the above table, e.g. a move from Stable to Stable - Early Adoption. This will be at the discretion of the clinic admin team and through consultation with ezyVet support. 
Customers cannot request to be moved to Bleeding Edge at this current stage - this is a select group that need to go through an authorization process to be applicable to this version type.

Most updates have very minimal downtime or are actioned outside of your main business hours/during the quieter periods. This downtime can vary depending on the size of the site and the size of the update.
Generally, this update process follows a 6-8 week cycle, depending on the below.

The size of the update - Not all updates are equal!

The updates we roll out vary in size, complexity and in what kinds of updates are included. For example, some updates involve new modules and features, other updates may be predominantly improvements to the existing system.
Some updates are therefore bigger in size than others.

The size of your clinic - Some sites need more time than others!

The size of a clinics site will often play a part in the amount of time it takes to update their system. For customers with very large sites where we have assessed there may be a potential for downtime will be contacted by ezyVet support to organize a specific time for updating to occur. This will mitigate the impact of the update for larger sites.

If your clinic is 24/7 or emergency

Should a clinic be a 24 hour, 7 day a week clinic, the ezyVet support team may contact these clinics to organize a time for updates that are large in size, or the technical team have noted there could be downtime during updating.

Should you know a specific day/time that is generally the quietest in the clinic or the best time to be updated, you can request this be set as your default update day and time for all future updates. Please contact ezyVet support with this information through the support button on your ezyVet site.

e.g Sunday at 3am is generally the best time for an update for my clinic, please log this as my preferred update time moving forward for each release.