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

Any plans to release new version? #75

Open
kloczek opened this issue Apr 7, 2023 · 8 comments
Open

Any plans to release new version? #75

kloczek opened this issue Apr 7, 2023 · 8 comments

Comments

@kloczek
Copy link

kloczek commented Apr 7, 2023

0.6.0...master shows now 35 commits since last release which was +4.5 years ago.

Do you have any plans to release new version soon? 🤔

@AsciiWolf
Copy link

@steve-m Please consider releasing a new version of librtlsdr. The current stable one is too old at this moment.

@wuch-g2v
Copy link

+1

@AsciiWolf
Copy link

The new version release is now even more important since the support for rtl-sdr blog v4 dongle was merged.

@martymac
Copy link

Hello,

Yes, that would be nice to get a new tag (I would like to be able to update the FreeBSD port, I've just got a request to update it).

Thanks in advance!

@kloczek
Copy link
Author

kloczek commented Oct 2, 2023

Gentle ping .. any update? 🤔

@IdotMaster1
Copy link

+1

@AsciiWolf
Copy link

@kloczek
Copy link
Author

kloczek commented Dec 27, 2023

Is it possible to start making github releases?🤔
On create github release entry is created email notification to those whom have set in your repo the web UI Watch->Releases.
gh release can contain additional comments (li changelog) or additional assets like release tar balls (by default it contains only assets from git tag) however all those part are not obligatory.
In simplest variant gh release can be empty because subiekt of the sent email contains git tag name.

I'm asking because my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages, which allows saving some time on maintaining packaging procedures.
Probably other people may be interested to be instantly informed about release new version as well.

Documentation and examples of generate gh releases:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
jbms/sphinx-immaterial#282
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
jbms/sphinx-immaterial#281 (comment)
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58

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

5 participants