I am concerned that this update breaks compatibility, yet is being done as a self review. Are there any other consumers of this library that could potentially be broken by this update? If so, how will this be dealt with?
What binding are you looking for? As I only see nevada/opensolaris mentioned, I am assuming minor. Can you mention the case number which contains the prior interfaces/bindings? Regards, Alan Hargreaves Yong Young Sun wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Update libchewing from 0.3.0 to 0.3.2 > 1.2. Name of Document Author/Supplier: > Author: Yong Sun > 1.3 Date of This Document: > 27 July, 2009 > > 4. Technical Description > > libchewing is a popular library for Traditional Chinese input method > engine > licensed in LGPLv2.1. And there are some input methods, like > iiimf-twle-chewing, scim-chewing depends on this library to provide input > services to users. > > The version currently shipped in nevada/opensolaris is 0.3.0, while the > community recently released a newer version, 0.3.2. In this new release, > the API/ABI compatiblities were broken, and some new features are added. > > iiimf-twle-chewing and scim-chewing had been updated to work with 0.3.2, > we therefore need to deliver the updated version to nevada/opensolaris. > > The interfaces (header files and shared library) remain the same as > before. > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > Globalization > 6.5. ARC review type: Automatic > 6.6. ARC Exposure: open > > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems
