[dev] Release Engineering: Versions 2

[Jan Schneider]

Zitat von Jon Parise <jon at horde.org>:

> On Wed, Dec 17, 2003 at 02:33:25PM -0500, Chuck Hagenbuch wrote:
>
> > > 1) One branch name for a major Horde version and all modules that run
> with
> > > this version, like FRAMEWORK_3 OR MAJOR_3.
> >
> > I find this more readable, and so I'd prefer it.

Not to say that the whole purpose of this new naming scheme is to avoid
confusion for our users in the first place. I guess the second solution
could even add to that confusion

> Agreed, and I prefer FRAMEWORK_ (or HORDE_) to MAJOR_.  HORDE_ makes
> the most sense because we've already defined 'framework' as our
> repository of packages while 'horde' refers to the global application
> "glue".

But we already have HORDE_ tag names for the release tags.
So, let's go with FRAMEWORK_3 for all modules that will be released with
Horde 3, okay?

> > > 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.
> >
> > I'd bee much happier if this looked like RELENG_3_IMP_4 or something
> like that,
> > so that the numbers and letters weren't squished together. Or
> > FRAMEWORK_3_RELENG_4, or what have you. I know it adds a bunch of
> characters,
> > though. And RELENG_3_4 seems too unclear. RELENG_F3_A4 (framework 3,
> app 4)?
>
> Agreed here, too.

Jan.

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