Question : Possible new release in 2022

[Tomawock]

Hi all,
i'm new to xclip and i'm really liking it and i appreciate the job that all of you have done to make it possible.
l wondered if a new release will be published this year.
I personally think is good idea since a lot of improvement has been made since the 9aa7090 , however i noticed that a large part of the last year's pull-request haven't been merged, analyzed or discussed, so i also think it should be maybe better to merge or discuss them before publishing a new release.
Hoping for an answer.

@hackerb9 @a1346054 @hwangcc23

[Delapouite]

Related ticket #122

[hackerb9]

I stopped being active with xclip when it became clear my vision for how it could work was too radical a change for @astrand, the author, for whom I have a great deal of respect. But I am checking in because this issue makes it sound like basic updates and bug fixes aren't happening.

@astrand: are you still around? Everything okay?

[astrand]

Hi, still around, but little time for this project nowadays, unfortunately. Yes, it is true that I prefer no radical changes right now. However, bugfixes and gradual, backwards compatible improvements are always welcome. And yes, I new release would be good. What do you all think of the latest master, is it considered stable so that it could be turned into a new release with little effort?

[hackerb9]

Unfortunately, I haven't used the mainline xclip in over a year, so I don't know anything about how ready it is. Last I recall, I had gotten the biggest bugs squashed and the remainder of what I had left to merge was more stylistic, like making -i and -o optional and improvements to the man page.

[hackerb9]

I've set mainline xclip as my default and I'm noticing a few bugs compared to my hackerb9 branch, but nothing huge. Things like not printing error messages when the old style "CUT BUFFER" is given more than 16 MB of data and xctest attempting to do exactly that and (of course) failing.

[hyder365]

How about 2023?

[victorbnl]

I’d like to see a new release as well. I was using version 0.13 and I had the issue that >= 1 MB images wouldn’t get copied, which has since been fixed. Hence my switch to using the git version. But I would like to switch back to stable releases as soon as possible.

I think there are more issues on the latest release than there are on the git main branch actually. Thus for me it would definitely make sense to make a new release now, even if minor bugs were to remain on the main branch, as there are in the latest release as well. The next release will not be exempt of bugs anyway, no matter how much it gets tested (and I think it has already been tested quite a bit), so I suggest making the release and then fixing the bugs in the releases coming after.

However, even if I consider making a release more urgent than thoroughly testing it, I can understand the desire to test it before making it. And I’d be happy to volunteer. The issue is I don’t know what needs to be tested. So if you tell me what testing is necessary, I’ll try to participate as much as I can.