Release management

Open randomthingsandstuff opened this issue 4 years ago • 3 comments

Would like to discuss release management for the project.

Currently we use simple incrementing release, but I'd like to have the ability to qualify releases against our test suite and tag them appropriately. Not every release should go through full cycle IMO.

Open to thoughts, etc. If we don't come up with some consensus, I will simply formulate what I think works best and move on by ~Late October, per my current testing plans.

Aug 17 '21 20:08 randomthingsandstuff

I've tagged our current master as v0.3.0 - a prerelease. I am down for going through a full cycle, and then tagging the result that as a v1.0.0 for production use. Your timeline works for me

Oct 15 '21 09:10 job

+1, Our test and release process would also very much appreciate version tagged releases.

Oct 19 '22 12:10 BenCastricum

Speaking about release, is there a reason for 0.5.1 not being marked as Latest on GitHub? I would like to be sure before updating Alpine pkg repo.

Sep 11 '23 11:09 androw