This is a companion discussion topic for the original entry at https://www.rstudio.com/blog/calendar-versioning-for-commercial-rstudio-products
RStudio is shifting to a calendar-based versioning scheme for future releases of all our commercial products.
We are making this transition to deliver a more transparent experience for our customers:
- The age of a given release will be self-evident from its version label.
- Customers can rely on support for a consistent and predictable time period. (Previously the support window was heavily influenced by how rapidly new releases superseded prior ones.)
- Customers will be able to easily determine which releases contain new features (as opposed to bug fixes), based on consistent standards for releasing new editions across all our products.
In this new scheme version labels are derived from the date of release using the YYYY.MM.patch format where
- YYYY is the four digit year
- MM is the two digit month
- patch is an integer that starts at zero and gets incremented each time non-functional improvements (e.g.: bug fixes, performance improvements, etc…) are made to the product.
We call the YYYY.MM portion of the version label the edition of the product. We will release a new edition of the product with a .0 patch number when new features are added and/or breaking changes have been made. Each edition will be supported for 18 months and the most recent edition will be supported regardless of its age.
Our support agreement has been revised to align with the new calendar versioning scheme. The changes will generally result in a more generous support window for both past and future versions. Please see our Support page for more details on these support windows.
To receive email notifications for RStudio professional product releases, patches, security information, and general product support updates, subscribe to the Product Information list by visiting the RStudio subscription management portal.