[dev] Release Engineering: Versions 2

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

| To sum this discussion up, there are currently two possible changes to the
| *branch* naming. The *version* numbers keep increasing by one, each module
| on its own.
|
| 1) One branch name for a major Horde version and all modules that run with
| this version, like FRAMEWORK_3 OR MAJOR_3.
|
| 2) Include the major Horde version that is required with the branch name of
| each module that still keep their major module versions, like RELENG3_4 for
| IMP 4.x and RELENG3_1 for Ingo 1.x.
|
| The discussion tended to the seconded solution, but I want to clearly point
| out the two possibilities before we decide. Opinions? Votes?

#2 sounds fine to me.  although Ingo 1.x should be RELENG2_1 since Ingo 1.x goes
with Horde 2 - Ingo 2.x is what will go with Horde 3.

michael

______________________________________________
Michael Slusarz [slusarz at bigworm.colorado.edu]
The University of Colorado at Boulder