Development is now formalised, with clean development and maintenance branches and a regular release cadence. Development is conducted via feature branches from devel. These are merged in following passing of unit tests run via GitHub Actions and a code review from a core developer. Releases are made at the end of each quarter from the then current, working version of the code in devel. This is merged across to the main branch, with longer regression tests run to further assure code quality and manage backward compatibility. A CalVer 52 versioning scheme is used, e.g. 2023.1.0 was the first release in 2023. Bugs and issues identified between releases are fixed via issues branches from devel, which are backported to main on acceptance. Patch releases from main are made within the quarter, e.g. 2023.3.1, depending on the number or urgency of the fixes. Separately, commercial partners operate their own release schedule based on forks and internal builds of the software from main. This process was developed in discussion with those partners, as the best balance between continual academic development of software, and the timely provision of stable, predictable releases that can be supported by OpenBioSim's developer resources.