Release cycles

The Vidjil project tries to keep agile develompent while producing certified, qualified healthcare software for clinical needs. See also our roadmap.

New releases with incremental changes may thus be deployed on-the-fly, but a notification is issued on the server. However, we announce the most significant features impacting data analysis with a 2-week notice.

Critical bug fixes can be deployed on both public and healthcare servers at any time. To help the development to move forward towards such stable healthcare releases, several freeze windows are enforced.

Summer release ☀️ Winter release ❄️
Meeting on release objectives mid-February begin-September
Dev: Main Freeze
Any new feature merge must be discussed.
30 March 31 September
Dev: Hard Freeze
No more feature merge, only bug fixes.
Polish strings, documentation, release notes, and announcements.
15 April 15 October
Deploy on the public server
Continuous deployment on the public server is freezed, except for critical bug fixes.
before 30 April before 30 October
Deploy stable release on healthcare servers and qualification
Continuous deployment on the public servers resumes.
June December

For server maintainers, the last stable release of the complete Vidjil platform is available on For bioinformaticians, the last stable release of the vidjil-algo analysis engine is available on