How often are release versions made?

The release frequency depended on the project and the development methodology used. In previous projects, we practiced:

• Weekly releases: Mostly on projects where Scrum or Kanban was used and quick delivery of functionality was required. This allowed for prompt feedback and faster response to changes.
• Bi-weekly releases (Sprint based): Typical for teams working with Scrum, where the release coincided with the end of a sprint. This provided a more predictable cycle and enough time for testing.
• Monthly/quarterly releases: Found in projects with a longer development cycle or strict regulatory requirements, where more extensive testing and approval processes were necessary.

Regardless of the frequency, we always aimed to ensure stability and quality of each release through a full testing cycle, including regression testing.