[dev] Re: [cvs] commit: horde/config hooks.php.dist turba/docs CHANGES turba/lib AbstractObject.php

[Jan Schneider]

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

> Quoting Jan Schneider <jan at horde.org>:
>
>>>   Log:
>>>   [cjh] Pass the Turba_AbstractObject to attribute hooks to allow access
>>>   to other attribute values (for example, to build a field's value
>>>   out of other fields).
>>
>> I guess we should mention this change in Horde's and Turba's docs/UPGRADING.
>
> Nothing should break, as far as I know, if hooks aren't changed though - it's
> just an extra argument that can be used if it's there.

Well, it would break if they use the new hooks, but didn't upgrade Turba.
It's just a configuration file change, so I wouldn't consider this a BC
break either, but it should be mentioned somewhere.

> If you meant just as a matter of notifying people/documenting it, then
> sure. Are
> the current UPGRADING files in HEAD where this would go? I'm not sure if I
> should restart them from scratch or add a seperate 3.1/2.1 section?

The latter.

Jan.

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