[dev] Release Engineering: Versions

[Marcus I. Ryan]

At this point, I think I actually prefer the RELENG<Horde Major Version>-<app
version> (e.g. Klutz RELENG3-1 and RELENG2-1).  There is a large enough
installed base of Horde 2.x and enough apps like klutz that can be fairly
easily backported/maintained that it makes sense to avoid any naming
conflicts.  This also seems a clean way to do it since Horde itself will just
have a RELENGx tag itself.

--
Marcus I. Ryan, marcus at horde.org
-----------------------------------------------------------------------
 "Love is a snowmobile racing across the tundra and then suddenly it
 flips over, pinning you underneath.  At night, the ice weasels come."
                 -- Matt Groening
-----------------------------------------------------------------------


Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
> > 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.
>
> For the record, I would be fine with this solution as well; I don't think
> it's
> critical to allow an app to jump major versions without jumping the
> framework
> version, and without the app version in the branch name, there isn't even a
> particular reason to do so.
>
> Also, with the new package setup, hopefully it'll take a *lot* to actually
> bump
> the major version of the whole framework.
>
> -chuck
>
> --
> Charles Hagenbuch, <chuck at horde.org>
> "I'm really... I'm not too fascinated by green food." - Average Joe
>
> --
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.