Bug 22910

Summary: [0.2] Add ABI padding/other future-compat stuff and release a shared library
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: tp-qtAssignee: Andre Moreira Magalhaes <andrunko>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: blocker    
Priority: high    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 22817, 23275, 23284, 23370, 24323, 24324, 24326, 24327, 24354, 24422    
Bug Blocks: 21340    

Description Simon McVittie 2009-07-23 09:26:06 UTC
17:06 < andrunko> smcv, also I would like to make tp-qt4 shared, so I can link 
                  the kde libraries with it, I have to change it locally to use 
                  the kde stuff
17:06 < andrunko> 0.2??
17:06 < andrunko> :D
17:06 < smcv> andrunko: how's our ABI?
17:06 < andrunko> smcv, mostly stable
17:06 < smcv> andrunko: I observe that you and grundleborg both broke ABI today
17:06 < andrunko> I don't t think there will be major changes anymore
17:07 < andrunko> smcv, we did, but we still can :D
17:07 < smcv> I think there should be at least one more 0.1.x release
17:07 < andrunko> ok
17:07 < andrunko> good :)
17:07 < smcv> the major blocker for 0.2 is adding virtual hooks / ABI padding 
              everywhere
17:08 < smcv> if we freeze ABI now, I think we should plan to not break it 
              throughout 0.3
17:08 < smcv> i.e. throughout 0.3 development, put in FIXMEs where we want to 
              break ABI
17:09 < smcv> then do one release where we fix the FIXMEs, bump the SONAME and 
              call it 0.3.99 or something, test it thoroughly, and re-release 
              it as 0.4
17:09 < smcv> does that sound sane to you?
17:10 < andrunko> yep, sounds good
Comment 1 Andre Moreira Magalhaes 2009-10-06 13:11:46 UTC
Change build system to generate a shared library
Comment 2 Andre Moreira Magalhaes 2009-11-10 07:13:55 UTC
Released

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.