New Prosal [was Re: policy change related to kdelibs snapshots]

[Dirk Mueller]

On Tuesday 11 July 2006 18:55, Aaron J. Seigo wrote:

> > separate branch (Kmessagebox broken? yay! KSystemTray changed in a very
> > incompatible way all at once? yay!).
> *sigh* this is how rumors get started.

Sorry, these were just two random examples. I'm sure I can come up with 
others:)

> personally ...... i don't see the problem with app developers simply not
> updating kdelibs so bloody often. keep your libs and other modules old and
> just work on your own stuff, and update everything every few weeks. a
> little self-discipline would go a _long_ way here.

The problem is that they can't commit when they don't update beforehand 
(assuming that there has been something ported against this particular 
application).

> this discipline by providing an API change timeline which could be as
> simple as routine messages to k-c-d noting API changes. these should
> include what changed, why it changed and who was involved (e.g. "who
> reviewed this change"). it would be trivial via a script to go from that to
> a little timeline that could be uploaded to a website somewhere. thoughts?

First we should agree on getting API changes scheduled and not just happening 
in a random fashion (like it was proposed in this very thread), *then* we can 
think about making all shiny and come up with a semi decent schedule. 


Dirk