EPR development follows an agile development process with 1 two week sprintsSprint cycles. EPR upgrades are rolled out automatically for minor and patch releases as these updates are bi-monthly and ad hoc or as needed basis for issues categorized as “security” related or critical “patches” which may severely impact customer business. For minor and non-critical patch releases which are non breaking changes, we release every two months into Production. EPR follows the Semantic versioning (also referred as SemVer). Software updates have always been a problem for software developers, release managers and consumers. Having a universal way of versioning the software development projects is the best way to track what is going on with the software as new plugins, addons, libraries and extensions are being built almost everyday.
...