[Xcb] Roadmap for next release of XCB (proto and libxcb)

[Christian Linhart]

Hi Jaya,

Thank you for offering to do the ABI/API checking for extensions other than XInput.
You can pick any extensions you like. Please post here which extensions you
are working on so that others can focus on other extensions.
Obviously, extensions that have modifications in their xml since the last release
are more important to check for ABI/API issues.

There are tools for ABI/API checking such as abi-compliance-checker.
These tools can help you to quickly screen the ABI/API compliance state.
Then you can focus on the stuff that these tools complain about,
and test/review that code to see whether that's a false positive
or whether that's really an ABI/API compliance issue.

Regards,

Chris

On 2016-01-07 08:34, Jaya Tiwari wrote:
> Hi Chris,
>
> I can take up the work with :
> *maybe implementing a solution for ABI/API issues with other extensions, when such issues are detected by QA work.
> As I had previously done QA(basically writing test application) work on API/ABI compatibility for render extension.
> Solution can be proposed once there is any incompatibility detected.
>
> Regards,
> Jaya
>
> On Thu, Jan 7, 2016 at 12:55 PM, Christian Linhart <chris at demorecorder.com <mailto:chris at demorecorder.com>> wrote:
>
>     Hi,
>
>     Now that Michael Stapelberg wrote that the next release seems to be still a while away based on discussions with me, I'd like to describe the state for the next release, so you get an idea what "still a while away" means.
>
>     The commits that I have pushed yesterday fix some of the issues that need to be fixed before we can make a release, such as: * the bug with align-offsets,
>     * and the lengthless lists implementation. This avoids future ABI/API issues where lengthless lists are used.
>
>     But there is still something to do:
>     * general QA work, such as testing and ABI/API compatibility reviews.
>
>     * I will soon post a proposal about how to solve ABI/API issues which arise from bugfixes in the xml-protocol definition.
>        (It's already partially written. It is based on the brainstorming we had a while ago about this issue.)
>       Then the proposal (or other possible solutions) can be discussed, so to get a design decision on how to solve these issues.
>       We'll need to solve such issues for the next release as I have learned a while ago.
>
>     * based on the ABI/API issues proposal and discussion:
>        implementing a solution for the ABI/API issues with XInput.
>        XInput is not built by default, but it is shipped with some Linux distros.
>        So we have to ensure at least ABI compatibility.
>        I am currently making a list of all ABI/API issues with Xinput.
>
>     * maybe implementing a solution for ABI/API issues with other extensions, when such issues are detected by QA work.
>
>     * checking Patchwork for patches that have been forgotten but should be included.
>
>     If you want to work on any of these points, please post this here, so we can coordinate who does what. (and avoid duplicate work).
>
>     I am working on the following stuff now:
>     * writing a proposal for handling ABI/API issues that arise from bugfixes in the XML protocol descriptions.
>        I plan to post this before next Monday.
>
>     * making a list of ABI/API issues with the XInput extension.
>
>     Cheers,
>
>     Chris
>     _______________________________________________
>     Xcb mailing list
>     Xcb at lists.freedesktop.org <mailto:Xcb at lists.freedesktop.org>
>     http://lists.freedesktop.org/mailman/listinfo/xcb
>
>
>
>
> -- 
> Regards,
> Jaya
>
>
> _______________________________________________
> Xcb mailing list
> Xcb at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xcb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/xcb/attachments/20160111/07d35c88/attachment-0001.html>