Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

Going 1.0

By Sean Roberts | 27 February, 2017

A Message from the Engineering Team

Up until this point, we have lived in a < 1.0 world. We have focused on shipping quickly and pushing innovative changes regularly. However, we realized that we are not fulfilling our commitment of clear versioning and expectations of backward compatibility. We also know that a system that is not living up to a clear versioning scheme can be perceived as a perpetual beta product or sub-production ready. Having over 1 Million annotations created by users and over 60 production releases (representing over 20,000+ commits) – it’s time to make our versioning match the maturity of our offering. So today we are turning 1.0 and with that, you will see the same level of quick development but with increased effort on making it clearer to users and platform developers what changes are being made and the level of impact you can expect from those changes.

Share this article