Recently we found some cases/issues that base/middleware packages changes ABI 
but application developers don’t know at all. It’s bad and dangerous. 

So, once a package update/upgrade involves a ABI changes, before submitting to 
T:T, please send an notification to meego-dev and meego-packaging and let 
release engineers know with detailed information of 
 * what has changed,
  * what are required to do in upper stack to work with the ABI changes

Same applies with API changes, especially for those very basic packages many 
packages use as Build dependencies, please let public know. To get know which 
packages are rely on your package, you could use localcheckbuild tool, and osc 
native command of  whatdependson 

Peter
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to