Hi!

I agree. We've recently merged some fixes that remedy compile issues on
modern systems. I have a few PRs in my queue to test & review, but
honestly I agree we could make a service release now and perhaps set up
some semi-regular release cadence, even if it is a few features/fixes
here and there.

Soeren, how do you feel about it? I'm not sure how difficult the release
process is, but I can grab the documentation and see if I can make it
work, at least testing all the processes.

I'm mostly worried about building installer packages, in my experience
that always breaks if there hasn't been a release for a long time. In
this case, I would suggest to release a version and build the installers
after the fact if possible.

Regards,
Ladislav

On Fri, Jan 23, 2026 at 03:20:00PM +0100, Jan-Benedict Glaw wrote:
> Hi!
> 
> I noticed that the sigrok and pulseview versions in Debian are
> horribly outdated. While the AppImage files work, I'd love to see a
> somewhat current version show up in Debian. As it seems, the main
> issue is that there are no recent releases in
> https://sigrok.org/download/source/pulseview (latest release tarball
> is nearly six years old) or
> http://sigrok.org/download/source/sigrok-cli (nearly five years old).
> 
> Guess it wouldn't hurt too much dropping a release tarball every now
> and then?
> 
> Thanks,
>   Jan-Benedict
> PS: Just used it to snoop on a traditional 50pin 8bit narrow SCSI-2
> single-ended bus, that worked perfectly well using the AppImage stuff.
> 
> -- 




> _______________________________________________
> sigrok-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sigrok-devel


-- 
S pozdravem Ladislav "Krakonoš" Láska                http://www.krakonos.org/


_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to