Liberation Politics

overview the purpose of this policy is to describe the release and update cycles for 4biz oxygen products , customer notifications, and other relevant information the policy guidelines apply to all our products, whether they use the saas or on premise model release and update cycles our product release and update proposal has been defined to provide stability, quick responses to issues, and continuous delivery of new features and experiences 4biz oxygen products generally follow three types of releases, as listed in the table below release type scope frequency notification major release new functionalities and killer features for the product typically, twice a year typically, one month before the release, with a second notification 20 days after the first minor release includes, but is not limited to, minor improvements, security updates, and generally does not involve architectural changes typically, once every 2 months planned hotfix updates including bug fixes and specific adjustments typically, once a month critical hotfix emergency fixes to ensure the stability and security of the system whenever necessary a few hours before, preferably 48 hours in advance the it central refers to each feature release and its associated hotfixes as a “series ” for example, version 7 6 5 4 is part of series 7 series are version updates, mostly with significant changes in the application or architecture as a result, 4biz oxygen products use the following versioning pattern series > major release > minor release > hotfix for example in version 7 6 5 4, 7 is the series, 6 is the major release, 5 is the minor release, and 4 is the associated hotfix 4biz oxygen release schedule release month release type version number january planned hotfix \<series> x 1 1 february minor release \<series> x 2 0 march planned hotfix \<series> x 2 1 april new series or major release series 0 0 0/ \<series> x 0 0 may planned hotfix \<series> x 0 y june minor release \<series> x 1 0 july planned hotfix \<series> x 1 y august minor release \<series> x 2 0 september planned hotfix \<series> x 2 y october new series or major release series 0 0 0/ \<series> x 0 0 november planned hotfix \<series> x 0 y december minor release \<series> x 1 0 ( ) the timing and frequency of releases are subject to change at the sole discretion of it central in case of changes to this schedule, customers will be notified in advance supported versions our current policy is to support the most recent series the previous series will be supported for up to 6 months after the release of the new series we generally perform two major releases per year; thus, customers will need to update approximately once a year to remain on a supported version it central provides updates (e g , patches and hotfixes) only for the supported version additional information on updates the update procedures depend on the model of the purchased solution (saas or on premise); for each of them, follow the recommendations below saas customers customers can schedule software updates as needed by submitting a new service request through our support website in this request, the customer specifies the desired update date, the desired version, and whether the environment is non production or production downtime is scheduled to minimize disruption to the customer's business the entire update process is handled by it central's support team on premise customers in this case, customers are responsible for software updates we recommend that customers test functionalities and customizations in the non production environment before updating the production environment guidance on how to update or use new features will be available in the release notes if you have any questions about the update procedures, please send us a service request through our support website