Release new version and / or update stable branch

[exterm]

Pre-submit checks

• [X] I checked for similar issues beforehand, but could not find any. I could not add my proposal to any existing issue.
• [X] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.

Feature description

The latest release is 2.2.0, which at this point is almost 2 years old. It looks like there's been a lot of changes happening on the master branch since then. Would it make sense to make some of those changes available in a stable version?

Proposed solution

Merge master into stable and release a new version.

Alternative solutions you considered

No response

Additional context

No response

[TheAssassin]

I plan one more feature for 3.0 (a really major release), I hope to release by the end of this month.

[exterm]

What's the feature you're planning?

[exterm]

Any help needed?

[TheAssassin]

I just tagged v3.0.0-alpha-1, which failed to build. An alpha 2 will be available once I fixed the packaging, which can be tested by users. I hope to release the final version soon.

[exterm]

Just writing to say I'm still interested in this :) Any help needed?