[dev] Mudules to release?
Robert Ribnitz
ribnitz at linuxbourg.ch
Fri Dec 12 07:06:47 PST 2003
>
>
>Date: Fri, 12 Dec 2003 13:01:21 +0100
>From: Jan Schneider <jan at horde.org>
>Subject: [dev] Release Engineering: Modules
>To: "Horde::Dev" <dev at lists.horde.org>
>
>With the next release cycle slowly appearing at the horizons, there are a
>few open issues that have to be discussed. I'll send separate mails for the
>different topic, here is the first one.
>
>We need to decide which from our over 40 modules will be released in this
>cycle.
>
>This is a list of all currently available modules, separated into four
>groups:
>
>1) modules that get released anyway, because we already have released them.
>
>horde
>accounts
>chora
>forwards
>imp
>kronolith
>mnemo
>nag
>passwd
>turba
>vacation
>
>
>
I currently have a (production, based on cvs aug 22) setup of:
horde
chora
imp
ingo
jeta
krononlith
mnemo
moment
nag
turba
From what I hear from my users, the killer apps that get used most are
imp, turba and kronolith
Keeping that in mind, I'd perhaps propose to do the following:
- individually release all modules of your categories 1 and 2.
- release a tarball 'common horde setup' (horde,imp, ingo, turba and
kronolith)
Most horde setup are used for web-based mail, so modules who help that
setup will probably be the ones people want most.
On the other hand, if some of the 'less common' modules get used more,
there'll be more feedback about them, and possibly more bugreports, etc.
Regarding version numbering, I think the idea to base versions on the
major horde release is a great idea, IMP 4.x will need the Horde
framework 4.x.
The above is of couse my personal opinion as a contributer of two or
three small things. I know my evnironment, I cannot speak for other users.
Robert Ribnitz
More information about the dev
mailing list