[dev] Release plan

[Jan Schneider]

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

> Quoting Jan Schneider <jan at horde.org>:
>
>> Agreed. This should be done before the BETA releases because I want them to
>> be as API stable as possible.
>
> Okay. Shall we just start going through everything in services/ and in
> framework/?

Probably, though I think we know the packages well enough to either feel
warm and comfortable or shiver by looking at the package names. ;-)

>>> The best example I have for this right now is the Text:: package - 
>>> there are
>>> functions that are in Text:: that probably should be Text_Filter 
>>> subclasses,
>>> and Text_Filter was never really sorted out. I'd like to move them all into
>>> Text_Filter before we freeze the API so that we're not forced to stick
>>> with the old "throw a function in Text::" for the rest of the Horde 
>>> 3 release life.
>>
>> Right, Text is a good example.
>
> Okay, but do you agree with what I want to do with it? :)

Yes, this is what I was trying to say.

>> Where does the new Date package stand? Do we use it already?
>
> Yes, Kronolith uses it.

And do you feel it's complete/stable enough to not require API changes any
time soon? I haven't looked at it at all yet.

>> Relationship probably needs more work and being integrated into the
>> applications?
>
> Definitely.

Jan.

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