Release strategy

[VictorIreri]

Hey @Malinskiy it's been a few months since the last release and so I was wondering, when can we expect the next release? Is there a release strategy and if not, should one be created?

[Malinskiy]

Hey @VictorIreri. Thanks for raising this topic.

At the current moment each develop commit is published to sonatype snapshots. The numbered releases are triggered manually using git tags which then get published into maven release as well as github release CLI tarball. The update of the brew tap is done manually.

0.8.0 is a very large release that took almost half a year to make. Most of the work is done single-handedly and I have to also balance my day job with the open-source. Good news is that all the features are already merged and the only thing left is to fix the test count expectation problem.

If you have suggestions on the release strategy that work for a single maintainer I'd be happy to consider them. Most of the slowness is because of the large scope of work and time limitations.

[VictorIreri]

Hey @Malinskiy. Thanks for your dedication to this project.
I guess what I'm asking is, how do you decide when to create a new numbered release and have you considered a more frequent/consistent "Beta" release, independent of the volume of work done? I don't know how much effort it is to create such a release but would a monthly Beta, for example, make sense to give users access to new features and fixes sooner and therefore give you feedback sooner?
Are those snapshots you mentioned available to download somewhere? Sorry, I'm not familiar with how they're set up.