Updates to the OpenTalk release process

[Wolfgang Silbermayr]

It's been quiet here lately. One of the reasons for that was some
restructuring of the development and release process. We've been evaluating
this new process in the OpenTalk team, and it proved to work nicely for us, so
it's just about time to create some transparency.

The OpenTalk Release Policy has been updated to reflect the changes.

https://docs.opentalk.eu/releases/policy/

We work in development iterations of three weeks, and in the past we tried to
cut a release after each development iteration. That didn't work out due to
the significant amount of work that went into QA, and the lack of focus for
specific features in a particular release.

Since the beginning of 2025, we started combine four of these three-week
iterations, resulting in this schema:

- One feature release around the end of each quarter of a year (e.g. 25.2,
   25.3 etc). We can't guarantee a specific release date with the current
   process, because we prefer ironing out issues that come up during the
   stabilization phase over shipping at a specific due date.
- Each feature release is supported for six months after it got released.
- During that support time, we create patch releases (e.g. 25.2.1, 25.2.2 etc)
   with bug fixes and security fixes, but do not include new features.
- Patch releases can be deployed without requiring extra configuration
   changes, these only happen in feature releases, unless explicitly required
   for a fix to become effective.

That said, expect more release announcements on that mailing list again in the
future.

Best regards, Wolfgang.

-- 
OpenTalk GmbH
Schwedter Str. 9a, 10119 Berlin

https://opentalk.eu

Tel: 030 / 405051-45
Fax: 030 / 405051-19

Amtsgericht Berlin-Charlottenburg - HRB 225352 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin