[dev] Release Engineering: framework distribution

Jan Schneider jan at horde.org
Mon Jan 19 13:29:26 PST 2004


Zitat von Michael M Slusarz <slusarz at bigworm.colorado.edu>:

> Quoting Chuck Hagenbuch <chuck at horde.org>:
> 
> | Quoting Jan Schneider <jan at horde.org>:
> |
> | > 2) create-symlinks.php
> | > We copy the modules into a directory inside the Horde tree in the same
> | > manner as create-symlinks.php creates symbolic links and change the
> | > HORDE_LIBS constant to point to this directory before creating 
> the tarball.
> | >
> | > I tend to the second solution because it's as easy as today for 
> the admins
> | > to install the Horde tarball. Opinions?
> |
> | I agree.
> 
> I asked this question before, and it was probably answered, but I 
> guess I still
> don't get it.  The question is: How are translations/template files 
> supposed to
> be packaged with the module they are associated with?
> 
> Two examples - I change a gettext string in a module, and we release 
> an update
> of this module.  How are the translation strings going to be updated (are we
> going to move translations for each module into the particular module?)

As we probably won't support packaged releases with the first new major
versions, this isn't something we need to decide now. But for the
translations we probably should stick with the current way and release them
together with tarball releases.
If we have packaged distributions that can be installed by PEAR or another
installer, we could as well package the translations seperately and release
them whenever a translator makes an update.

> Example two - I am working with Horde_Tree and add/change/delete 
> functionality
> tha alters the templates.  However, the templates live in horde/templates. 
> What to do about this?

This is a bit harder and I don't know a quick solution for that. I guess the
packages that need templates or other stuff (graphics for example) that
live in the document tree, we need an installer capable of installing such
files anyway before the packages are useable.

In case I didn't make this clear in the past, the first versions of the
releases will still be good old tarballs. Anything else would retard the
release date too much.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - Neue Wege des Lernens
http://www.tip4all.de - Deine private Tippgemeinschaft


More information about the dev mailing list