Guake 3.8

[Davidy22]

It's been a long while since last release and we've gotten some hefty features/fixes in. The older pull requests are mostly cleaned out now, just some that need work are left. I do particularly want to get #1897 in to finish dealing with something that looks like it's been a heavy blocker for package maintainers, wouldn't mind getting some of my other pull requests in as well. Would like to have all the things we're going to have in the next version merged in for a little while and frozen so we can use it day-to-day to make sure 3.8's clean, a release after this amount of time might get attention. Don't have access to any keys and I probably don't know all the channels guake has to get a new package out, but I do want to get the currently unofficial ppa on board with us so we can give people who want ppa a link ourselves, and polish off the highest voted request on feathub.

[gsemet]

Usually, packager acts on their own will, so when I release on pypi the package are updated a few weeks later. some distrib like debian has weird policy (they never update a package except patch fix, so guake 3.8 won't be available in already released versions).

I would like the following actions to be made before release, tell me if you can do it:

• update all dependencies (make update), and also update pipenv pip etc in the build environment. I do not have a linux env so i cannot do it easily
• some tests of course

on it is ok, I can do the release and push to pypi. (should be automatic through the pipeline, I will check it).

also, I would like to recommend installing guake through pipx, I hope it works, but I cannot confirm. Can you test if old version of guake works with pipx?

[Davidy22]

Alright, the dependency update's been done, now just dogfooding. pipx still not recommendable because of the dependency outside of the python ecosystem.

[mlouielu]

How about poetry?

They also provide poetry publish and poetry publish -r testpypi for publising.

[gsemet]

Thanks a lot for the update. For the poetry migration, this is not too difficult but we can do it after the next release.

[mlouielu]

Sure, no rush on this.

[mlouielu]

I've fix #1894 by #1907, if merged then +1 for 3.8 release.