[SERVER-1662] API/ABI compatibility for C++ client library between point releases Created: 23/Aug/10 Updated: 29/May/12 Resolved: 25/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | 1.6.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Roman Shtylman | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
For developers using the c++ client library, it is important that point releases try to maintain ABI/API compatibility between point releases. This makes it easier for the client library bug fixes to be deployed when applications are linked against the shared library version of the client library. Until that is available, it would at least be nice if the website documentation mentioned something on the matter (e.g. that ABI/API compatibility is not maintained and what the advice is for upgrading through point releases) |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 25/Sep/10 ] |
|
Duly noted. |