Missing Release cycle documentation

[kratkyzobak]

Issue description

There is approx one version minor version per year and few patches. Currently, it's approx 8 months from last release with 20 merged PRs, some of this being bugfixes (so patches)

I did not found any information, about release cycle of this project, so I want to ask, what is planned cycle of releasing at least patches and/or backporting bugfixes into older versions to patch them.

I think, some info in CONTRIBUTING.md would be nice, even if it is "Don't ask. We will release new version when we can."

[methane]

We have adopted a rule that requires review by others before merging pull requests.

However, we currently have only two maintainers who are irregularly active. Even when one maintainer is active, it's not guaranteed that the other can actively review.

This applies not only to the master branch but also to maintenance branches.

Therefore, I cannot design an executable schedule, nor do I have the motivation to design an unworkable schedule.

Here's what I can say. We have one master branch and one maintenance branch. Immediately after a new version release, we focus on bug fixes. When we start implementing new features, we create a maintenance branch and backport critical bug fixes.

[kratkyzobak]

Thanks for reply.

Based on schedule - would it be possible to release 1.8.2 with current bugfixes?

I'm willing to help with preparing branch from 1.8.1 and cherry-picking bugfixes from PRs created since 1.8.1. Only problem could be, that I may have different opinion on what is bugfix.

[methane]

Are there any bug fixes that you need in the master branch?

I am focusing on zlib compression and any help make me slower.

[kratkyzobak]

I'm currently experiencing problems with another library caused by merged #1625 which is not released as version. If new version would be released, I can make PR to bump version in library.

[methane]

I can not promise new version to you. But if you create PR, I will check and merge it.

Anyway, use master branch if possible. It obviously helps us.