Roadmap for the project

[heuer]

As I get a little more involved with the project, I'm wondering if another 0.16.x release is planned, or if we should focus on 0.17.x, which will bring some changes anyway.

I would prefer a final release under 0.16.x (maybe addressing #144 and #146 and all previous changes), maybe fixing #134 and #141 might be a useful addition.

But I would probably want to concentrate on wlroots 0.17.x

Do you have any roadmap for this project?

[flacjacket]

Thanks for the question! There isn't a particularly firm roadmap for the project other than to serve the needs of whatever libraries are using it and ideally stay as up-to-date as possible. The main user I know of is qtile, but there could be more that I don't know about, so any changes on 0.16 should at least not break that. If there are some good changes to make on 0.16 then I'd be happy to cut a release with those based on all of the PR's that you have put up. Whenever 0.17 is able to compile, we can cut over the main branch to that (there is some work in that direction in the 'wlroots-nextbranch that @m-col started, but it still needs some work AFAIK), but even then, there is the0.16.x` branch that we can cut releases off.

[heuer]

Thank you for your message. Another 0.16.x release would be great.
I will probably submit another pull request for the OutputState API (issue #149), but it should be compatible with all previous 0.16.x releases.

I have a project that is based on pywlroos and it would be nice if I could specify a fixed pywlroots version, since I also rely on some boolean return values etc., which is currently only implemented in the main branch.

I'll look into the OutputState API and come back to you.

[flacjacket]

Sounds good! I'll work on merging your other open PRs in the meantime, just let me know when would be convenient to cut a release!

…

On Sat, Mar 16, 2024, 07:45 Lars ***@***.***> wrote: Thank you for your message. Another 0.16.x release would be great. I will probably submit another pull request for the OutputState API (issue #149 <#149>), but it should be compatible with all previous 0.16.x releases. I have a project that is based on pywlroos and it would be nice if I could specify a fixed pywlroots version, since I also rely on some boolean return values etc., which is currently only implemented in the main branch. I'll look into the OutputState API and come back to you. — Reply to this email directly, view it on GitHub <#148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFGJBIARB7D5P5B7OFFH3DYYQWEZAVCNFSM6AAAAABETALCDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRHE3DANRUGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[heuer]

I submitted a PR #171

If no further bugs are found, this would be the last change I want in another 0.16 release.

[heuer]

@flacjacket, do you think you'll find time for a 0.16.7 release? At least a release candidate would help. A few PRs have now accumulated.

If I can help you with this, let me know.

[flacjacket]

Sure! Sorry for letting those pile up. Is there anything else that would be good to get in for a 0.16 release?

[heuer]

Thank you! I will update the CHANGES.rst and think that nothing will stand in the way of a new release.
I would like to implement a few more protocols, but that can wait till another release. Either another 0.16 or 0.17 release.
OutputState and the changed API regarding the boolean values vs. exceptions are important.

I'll provide a PR for the CHANGES.