[horde] RELENG 3

Chuck Hagenbuch chuck at horde.org
Mon Dec 27 11:27:15 PST 2004

Quoting Barsalou <barjunk at attglobal.net>:

>>> However, if the final releases are going to be separated out in each of
>>> their individual directories...then I will work with that.
>> Of course, The existing RELENG snapshots are still snapshots - 
>> they're just of a different branch. They're not tested, they're not 
>> guaranteed to parse, etc.
> I didn' realize the they weren't the "release" version.  So what does 
> the RELENG branch represent then?

The RELENG branches are release branches - not actual releases. EVERYTHING in
the snaps directory, no matter what branch it's from, is just a snapshot - it
is created automatically, it might be created in the middle of a commit,
between commits, with a parse error - anything. They're a convenience for
people who don't want to use CVS for some reason or another.

On a more general level, RELENG is where commits are done for the 
versions that
became IMP 3.2.1, 3.2.2, etc. The FRAMEWORK_3 branches serve the same purpose
for all applications that work with Horde 3.

>>> When I go to http://ftp.horde.org/pub/  I can find the application
>>> tarballs, but don't see framework.  Is it being tarred up with horde?
>> Yup.
> Is it still called framework? ( I don't see it in the horde-3.0 
> tarball ) Do I still need to run the install_packages script?

It's in lib/.

> What other differences are there from the way HEAD was working before it was
> released?

The only one is that it's not HEAD, so some incremental upgrade scripts aren't
present (just the ones from the last stable versions), and the 
framework files,
for all tarball releases (NOT snapshots) are installed for you into horde/lib,
with the small modification made to horde/lib/core.php for that to work


"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams

More information about the horde mailing list