![]() Here, the term “compatible” generally means to preserve the essential function, possibly with some improvements. A software system is backward compatible if it accepts and processes any input from a prior version in a “compatible” way. ![]() Versioning and compatibility in AzureĪ key concern in software versioning is backward compatibility. This blog post explores the philosophy of the Azure Breaking Change policy and the process and tools we use to ensure that it’s followed. We recently published an overview of this policy in the Azure Developer Center on Microsoft Learn. Azure has developed detailed policy for allowed changes in service interfaces and behavior and a process for enforcing these guidelines. ![]() Azure’s approach to versioning and avoiding breaking changesĪzure is dedicated to avoiding “breaking changes”-changes in service behavior that result in failures or unexpected behavior in production customer applications. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |