Hi list, Some four months, two weeks and a day ago we released version 1.0.28 of the sane-backends[1][2]. A week later, I posted[3] a janitorial in which I said I wanted to
- release on a 4 to 6 month schedule after 1.0.28 - switch to Debian 10 for source tarballs - squat all compiler warnings on Debian 10 - update our documentation So, in terms of time schedule, we should start thinking of releasing 1.0.29. We've just acquired a new backend (and have another in the pipeline) and there have been close to 900(!) commits since 1.0.28. Our source tarballs are built using a minimal Debian 10 Docker image already. In the compiler warning department[4] things don't look as good. I've been a bit busy with other stuff like triaging new issues, reviewing merge requests and converting the SANE Standard to Sphinx reStructuredText, apart from my non-SANE activities. [1]: https://gitlab.com/sane-project/backends/-/releases [2]: https://alioth-lists.debian.net/pipermail/sane-devel/2019-July/036919.html [3]: https://alioth-lists.debian.net/pipermail/sane-devel/2019-August/036957.html [4]: https://gitlab.com/sane-project/backends/issues/120 Despite of a somewhat visible lack of progress to the above goals I set (for myself?), I suggest targetting 2020-01-20 as the release date for 1.0.29. How does that sound? Hope this helps -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join
