[dev] Release Engineering: Versions

[Jan Schneider]

With 30+ modules eventually being released, we need to think about our
branch naming. We would have stable branch names from RELENG_1 up to
RELENG_4 and a pretty complex matrix of which versions goes with which
other modules.

Already now a lot of people are confused about which versions work with each
other, and even I have to think a few seconds before I can tell. For some
modules I rarely use I even don't know at all off my head.

Additionally we have two modules (Ingo and Klutz) that already have a
RELENG_1 branch but no releases, so that the first releases of these
modules have to be 2.0 or we would release the 1.0 versions from RELENG_2
branches. Still following? :-)

As the possible combination of module versions mainly depends on the Horde
version, I suggest a new brach naming theme that is based on the major
Horde version. Something along MAJOR_3 OR FRAMEWORK_3 for all stable
branches of to be released modules and *_4 when the next Horde version
comes out.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft