Keeping binary compatibility

[Ivan ?uki?]

> these rules on the techbase and use tools that detect BIC issues. Can't 
> we integrated the abi-compliance-checker with krazy and send mails to 
> the maintainers of those libs whenever a BIC change is detected?
>  Similarly, we could add the BIC verifying step to the release checklist 
> and hold back the release until the BIC change is reverted (for kdelibs 
> or other libs guarantiing BC), or the SO name is increased. I think 

+1 for this. It is sometimes hard to keep in mind all possible BC issues, and from time to time those have to creep in.

Cheerio
Ivan

-- 
Progress isn't made by early risers. It's made by lazy men trying to find easier ways to do something.
  -- Robert Heinlein