picking up all changes from khtml-cvs, discussing changes less here

[porten at froglogic.com]

On Fri, 7 Nov 2003, Darin Adler wrote:

> On Nov 7, 2003, at 7:41 AM, porten at froglogic.com wrote:
>
> > The two possible point of failures mentioned above would of course
> > already be caught if you were just monitoring khtml-cvs. To get
> > notifications saying that something has happened. This list would be
> > the place for questions and details then.
>
> I think this is where our opinions may differ. It puts more burden on

Not that much ...

> the recipient if he's expected to read the cvs log and ask questions.
> Conversely, it puts more burden on the sender if he's supposed to
> actively call attention to changes. I'd prefer to continue to use a
> "push" model rather than "pull".

That's what I agreed to in the end. I wanted to to describe a model where
khtml-cvs would just be a safety mechanism for things not discussed here.

The number of Konqueror contributor is rather large. Some of them just
occasionally do work and it will be impossible to catch all those cases.
That's why we started to add ChangeLog entries for you to be able to
follow what has happened.

Harri.