[dev] Horde 5 was: Re: [commits] Horde branch develop updated. fa956a4d83a7227e2a5d47bfe87185854e151fbc

[Ralf Lang]

> * The issue with me jumping major versions (despite Firefox/Chrome's
> attempt at a paradigm shift) is that it suggests there are going to be
> major changes to installation and config. I don't believe that is going
> to be the case. Most of the things that will be changing will be
> core-stuff; looking at 4.1 (or 5.0) as an end-user, you are really not
> going to notice a difference.
>
> Maybe this is just an educational thing. But I wonder if some users will
> be a bit hesitant to upgrade solely because they fear things are going
> to break.

You're going to notice changed UI. On the contrary, when Horde 4 changed 
to pear-based installation (good thing!) a lot of users did not expect 
their old unzip-one-file installation model won't work any more.

> * I would like to see a bit more clarification regarding what Horde 5
> means. Because it is a bit confusing at the code level since it really
> is no longer horde (the application) that is important, it is Horde_Core
> (the package). Not sure if we can, or should, do anything about that for
> purposes of keeping things simple for the customer.

Horde 5 - bc-breaking horde base release. From a user pov, base probably 
means the libraries+horde (base app)+content+timeobjects. I'm not sure 
about the latter. The major horde number tells me if an upgraded app or 
library is designed to work with my setup.