2.8.x / 2.9.x release?

[SinisterRectus]

I just noticed that there is a tag for 2.8.0, but no release, and therefore no luvit release that contains luvi 2.8.0. Is this intentional?

[rphillips]

Not intentional. The build machines have been gone for some time. It would be nice to get travis to push images.

[SinisterRectus]

My experience in building C software doesn't extend much further than gcc -o hello hello.c. Wish I could help here.

[rphillips]

@SinisterRectus which platform are you interested in?

[aiverson]

I have a decent amount of experience in compiling and writing C software as well as devops stuff. I can potentially help out here.

[SinisterRectus]

I personally develop on 64-bit Windows, but having my own copy of luvi 2.8.0 would not be helpful for my users, who I instruct to use the get-lit script(s).

Discord supports transport compression with zlib streams, so I was looking to test the new miniz bindings, but they have not made transport compression mandatory in their protocol, so it's not critical that I have access to this at the moment.

[rphillips]

Travis just added beta support for windows... We could potentially leverage that.

[rphillips]

This will help for Linux builds... #181

[joerg-krause]

There are already 46 commits to master since tag 2.8.0. Maybe it is time for 2.9.0?

[SinisterRectus]

2.8.1 or 2.9.0 might be appropriate, depending on what the changes are. Would probably be best to have a reliable build procedure for building 2.8.0 and then worry about the rest.

[joerg-krause]

We are stuck to version 2.7.6 in Buildroot, as it is the latest version which provides a release tarball. Unfortunately, this version does not compile with OpenSSL 1.1.x

I'd be delighted if there was a new release with a downloadable tarball for the source 🙏

Note, that I am not interested in any target binaries, but in a tarball containing all the source files (like luvi-src-v2.7.6.tar.gz).

[SinisterRectus]

This?

[joerg-krause]

No, as the deps folders are all empty.

[joerg-krause]

This.

[joerg-krause]

The Makefile already has the necessary target publish-src to upload a release tarball containing all the source files.

Maybe one of the maintainers can tag a release and run make publish-src, so we can get an updated version of luvi, which can be build with OpenSSL 1.1.1a.

[rphillips]

2.8.1 or 2.9.0?