On Sun, 3 Jun 2018 20:17:31 +0200 Harald Welte <laforge(a)gnumonks.org> wrote: 98. But I do not apply 0001-update-version-to-0.1.5git.patch so that the version stayed at 0.1.4. I added Alex Csete's patch Add-initial-support-for-Airspy-HF from his fork of gr-osmosdr for gqrx. And a trivial doxygen-reproducible patch that should make the reproducible-build folk happy. Please consider incorporating those before your next release tag. Let me second that! Release Early, Release Often! Bonus points for cryptographic signing or released source, either by using gpg with git to sign tags, or creating detached signatures of release source tarballs. 0.1.5 would still work fine. Due to steady C++ compiler changes and my aggressive bumping of gnuradio's soname and soversion for each gnuradio release, I have not been so worried about checking API and ABI changes with gr-osmosdr. Package dependencies make upgrades work smoothly. Some more details about Debian packages that may interest this list: As described in debian/copyright, in lieu of gr-osmosdr release tarballs, I use git archive --format=tar --prefix=gr-osmosdr-0.1.4/ v0.1.4 \ | xz > ../gr-osmosdr_0.1.4.orig.tar.xz to create the basis of the Debian source package. Then, to get more of your recent good work out of your git tree and into Debian packages, I use git format-patch v0.1.4 to generate a series that gets applied to the source tarball via Debian quilt patch format source packaging tools. But yes, that begins to get annoying with so many commits between tags. Thanks for all your good work on making gr-osmosdr so useable and useful! Your humble Debian package maintainer, -Maitland P.S. If you contribute to osmocom, some of my remarks I made at the last gnuradio conference, grcon17, apply to you too: https://www.youtube.com/watch?v=yKKjbT6YXgA Thanks again for all the good bits.

Dear Dimitri and Steve, On Sun, Jun 03, 2018 at 08:17:31PM +0200, Harald Welte wrote: is there anything we can do about the status/progress of gr-osmosdr, particularly in terms of tagging new releases? I understand that people do have a life and other priorities, and that those priorities change. But the fact that there's a Osmocom sub-project which is heavily used by people out there, and which is packaged by distributions yet we don't tag any releases for more than four years is also problematic. What can I do (or anyone else do) to change this? Sure, I could just push a tag to the repository, but I'm not a developer of gr-osmosdr and hence I feel neither qualified nor have any authority. Thanks for your time and help! Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)