Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] What's the release policy? #679

Open
Sil3ntStorm opened this issue Jul 17, 2023 · 2 comments
Open

[question] What's the release policy? #679

Sil3ntStorm opened this issue Jul 17, 2023 · 2 comments

Comments

@Sil3ntStorm
Copy link

It's been a while and around 190 commits have happened since the last release. It also seems a few issues have been resolved.

Wondering what the plans are for a new release?

Releases / tagged versions are a kind of a requirement for packaging the library and also make it easier to depend on them rather than using a random commit.

@tuexen
Copy link
Member

tuexen commented Dec 20, 2023

The last time I made a release, several people did not like it... So I'm a bit hesitating to do so.

@alvestrand
Copy link

Getting stuff that people don't like into specific named releases is actually an advantage.
Bug tracking databases like CVE very much like saying "this problem exists in version NN and is fixed in NN+1".

Release early, release often would be my advice :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants