GitHub release cycle

[baimafeima]

Could you make release here on GitHub a bit more frequent so that distributions can include updates sooner?

[PeterSurda]

I would like to do that and have been putting infrastructure in place to make it easier. However, currently I'm working on a major network redesign, and there are two critical bugs that I haven't be able to fix yet (a memory leak and a recursion overflow). That's the primary reason why 0.6.3 hasn't been released yet.

At least for Windows, there are automatically generated daily snapshots: https://bitmessage.org/download/snapshots/ . I hope to have OSX dailies as well when 0.6.3 is released.

[baimafeima]

Thanks a lot for your quick reply, this is very much appreciated.

At least for Windows, there are automatically generated daily snapshots: https://bitmessage.org/download/snapshots/ . I hope to have OSX dailies as well when 0.6.3 is released.

I don't use any of these two operating systems and snapshots don't matter too much as I rather wait for Bitmessage to be updated via the software centre of my operating system of choice.

[PeterSurda]

That's a valid point.

[g1itch]

Maybe you can introduce forth digit in the version and make some hook which releases when v0.6 is merged into master?

Distributions usually don't like to build packages from git snapshots and prefer releases.

[PeterSurda]

Man, what an excellent suggestion. It's a bit more complicated though as I'd have to create additional environments for windows/osx but I think it's worth it.

[g1itch]

Now it can be done with a github workflow, like I did in my branch ci: https://github.com/g1itch/PyBitmessage/blob/ci/.github/workflows/appimage.yml