New Prosal [was Re: policy change related to kdelibs snapshots]
dymo at mk.ukrtelecom.ua
Wed Jul 12 08:16:35 BST 2006
On Tuesday 11 July 2006 19:55, Aaron J. Seigo wrote:
> 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.
This does not work. Say, developer A is disciplined and keeps his old copy
of kdelibs and developer B is always using last changes from kdelibs.
Then the application won't compile for A and he will be forced to update
kdelibs. This scenario does happen!
> 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?
... and a comment on how to fix the compile with this new change ;)
More information about the kde-core-devel