[dev] Horde release cycle

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> And I am still a proponent of having an application be able to  
>> indicate that a particular PEAR/Horde library needs to be a certain  
>> version in order to work properly.  Not sure if that is still  
>> something we are considering.
>
> Yes, that should definitely be possible, and I agree it's a good idea.

That doesn't make much sense, unless it also triggers a number of  
major version bumps.
Unless we drop tarball releases completely, a framework package still  
is part of a Horde release. So we can't simply depend on a certain  
package version from an application, without also requiring a certain  
Horde version from that application. And this is a BC break, so it's  
only possible when we bump the major versions of 1) the package, 2)  
horde and 3) the application.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/