.. _techguide-release:release_process: Release Process =============== GNU Health stable versions (those with even minor number, eg 1. **2**.3) are released approximately every 12 months (on a Sunday). .. _techguide-release:release_process-stages_of_the_release_process: Stages of the Release Process ----------------------------- For each version, around two months before the actual release, GNU Health enters in a **feature freeze** stage, and a month before, Health enters in **code freeze** stage. At this moment, a **release candidate** version is created; and the demo community server updated and the translator teams notified. .. _techguide-release:release_process-upcoming_release_schedule: Upcoming Release Schedule ------------------------- The next stable GNU Health HIS node version will be **5.0** based on Trytond **7.0**. Estimate dates are the following, subject to changes. .. list-table:: :widths: 35 25 :header-rows: 1 * - Event - Expected date * - Feature freeze - March 23th, 2025 * - Code freeze & release candidate - April 27th, 2025 * - Release 5.0.0 - June 29th, 2025 .. _techguide-release:release_process-security_fixes: Security fixes -------------- The security fixes are not back ported to old releases. We just provide security fixes for the current major release |version|. .. _techguide-release:release_process-checklist: Checklist --------- As the project and its resources were growing very much over time we need a checklist to keep an overview what has to be uploaded and updated with any HIS release: * Uploads: * (Start with release candidates on TestPyPI) * PyPI packages for server, its modules, client and plugins * Tar ball + signature for the same as above * Demo database dump * Ansible * Virtual Machine image * RaspberryPi image * RPM/Zypper package * Docker image * Documentation: * Merge future branch with new functionalities * Versions in conf.py * Changelog * Roadmap * Release Schedule * Announcements: * Mailing List * Matrix * Mastodon