<div dir="ltr"><div>Hi Chris,</div><div><br></div><div>Yeah I can start with Render extension.</div><div><br></div><div>Regards,</div><div>Jaya</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 11, 2016 at 12:51 PM, Christian Linhart <span dir="ltr"><<a href="mailto:chris@demorecorder.com" target="_blank">chris@demorecorder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Jaya,<br>
<br>
Thank you for offering to do the ABI/API checking for extensions
other than XInput.<br>
You can pick any extensions you like. Please post here which
extensions you<br>
are working on so that others can focus on other extensions.<br>
Obviously, extensions that have modifications in their xml since
the last release<br>
are more important to check for ABI/API issues.<br>
<br>
There are tools for ABI/API checking such as
abi-compliance-checker.<br>
These tools can help you to quickly screen the ABI/API compliance
state.<br>
Then you can focus on the stuff that these tools complain about,<br>
and test/review that code to see whether that's a false positive<br>
or whether that's really an ABI/API compliance issue.<br>
<br>
Regards,<br>
<br>
Chris<div><div class="h5"><br>
<br>
On 2016-01-07 08:34, Jaya Tiwari wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">Hi Chris,
<div><br>
</div>
<div>I can take up the work with :</div>
<div><span style="font-size:12.8px">*maybe implementing a
solution for ABI/API issues with other extensions, when such
issues are detected by QA work.</span><br>
</div>
<div>As I had previously done QA(basically writing test
application) work on API/ABI compatibility for render
extension.</div>
<div>Solution can be proposed once there is any incompatibility
detected.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Jaya</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jan 7, 2016 at 12:55 PM,
Christian Linhart <span dir="ltr"><<a href="mailto:chris@demorecorder.com" target="_blank"><a href="mailto:chris@demorecorder.com" target="_blank">chris@demorecorder.com</a>></a></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
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.<br>
<br>
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,<br>
* and the lengthless lists implementation. This avoids
future ABI/API issues where lengthless lists are used.<br>
<br>
But there is still something to do:<br>
* general QA work, such as testing and ABI/API compatibility
reviews.<br>
<br>
* I will soon post a proposal about how to solve ABI/API
issues which arise from bugfixes in the xml-protocol
definition.<br>
(It's already partially written. It is based on the
brainstorming we had a while ago about this issue.)<br>
Then the proposal (or other possible solutions) can be
discussed, so to get a design decision on how to solve these
issues.<br>
We'll need to solve such issues for the next release as I
have learned a while ago.<br>
<br>
* based on the ABI/API issues proposal and discussion:<br>
implementing a solution for the ABI/API issues with
XInput.<br>
XInput is not built by default, but it is shipped with
some Linux distros.<br>
So we have to ensure at least ABI compatibility.<br>
I am currently making a list of all ABI/API issues with
Xinput.<br>
<br>
* maybe implementing a solution for ABI/API issues with
other extensions, when such issues are detected by QA work.<br>
<br>
* checking Patchwork for patches that have been forgotten
but should be included.<br>
<br>
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).<br>
<br>
I am working on the following stuff now:<br>
* writing a proposal for handling ABI/API issues that arise
from bugfixes in the XML protocol descriptions.<br>
I plan to post this before next Monday.<br>
<br>
* making a list of ABI/API issues with the XInput extension.<br>
<br>
Cheers,<br>
<br>
Chris<br>
_______________________________________________<br>
Xcb mailing list<br>
<a href="mailto:Xcb@lists.freedesktop.org" target="_blank">Xcb@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/xcb" target="_blank" rel="noreferrer">http://lists.freedesktop.org/mailman/listinfo/xcb</a></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>Regards,<br>
</div>
Jaya<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Xcb mailing list
<a href="mailto:Xcb@lists.freedesktop.org" target="_blank">Xcb@lists.freedesktop.org</a>
<a href="http://lists.freedesktop.org/mailman/listinfo/xcb" target="_blank">http://lists.freedesktop.org/mailman/listinfo/xcb</a></pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>Regards,<br></div>Jaya<br></div></div>
</div>