This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-sdr@lists.osmocom.org/.
Patrick Strasser-Mikhail patrick at wirklich.priv.atA. Maitland Bottoms 2018-06-03 21:54: > On Sun, 3 Jun 2018 20:17:31 +0200 > Harald Welte <laforge at gnumonks.org> wrote: > >> today I discovered that the gr-osmosdr package in debian unstable >> contains a whooping list of 96 patches. This is due to the fact that >> since November 2014 there hasn't been any tagged versions in the >> repository. > > 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. > >> >> I'd like to suggest to tag releases a bit more often. >> >> @horizon: What about jumping to 1.0.0 right away? > > 0.1.5 would still work fine. What do you think of Semantic Versioning (https://semver.org/)? > Summary > ------- > Given a version number MAJOR.MINOR.PATCH, increment the: > > MAJOR version when you make incompatible API changes, > MINOR version when you add functionality in a backwards-compatible manner, and > PATCH version when you make backwards-compatible bug fixes. > > Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. > FAQ > --- > [...] > How do I know when to release 1.0.0? > ------------------------------------ > If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0. > [...] gr-osmosdr being actively used for years now and already including dozens of patches and forked-tree features, it seems to me that 1.0.0 is completely warranted. If bugfixes and new features keep on coming, bumps in minor number and patch number seem to help make versions better comparable. BR Patrick -- Engineers motto: cheap, good, fast - choose any two One of the lucky 10.000: http://xkcd.com/1053 Use Mail Encryption Today! PGP Key ID: 0xDF8A127E5A120903 Patrick Strasser-Mikhail <patrick at wirklich priv at> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20180605/d851a7c7/attachment.bin>