Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Less messy way to make releases? #737

Closed
Tracked by #3143
Coolthulhu opened this issue Aug 1, 2021 · 2 comments
Closed
Tracked by #3143

Less messy way to make releases? #737

Coolthulhu opened this issue Aug 1, 2021 · 2 comments

Comments

@Coolthulhu
Copy link
Member

I usually mergetest a lot of PRs at once, then merge them one by one as I test them.
In current system, this results in a whole lot of tiny, empty releases. This is obviously not good.

I could try discipline and not merge until I test a whole batch, but that sounds tedious and prone to mistakes.
I could also try merging my mergetesting branch onto main and pushing that, but it only works if all of the tested PRs are ready.

Ideally, there would be a way to:

  • Delay releases to something like 1 per day, if something was merged this day
  • Automatically delete empty releases and append their changelog to the first complete release
  • Detect partly-cancelled releases (cancelled when only some of the builds completed) and treat them like empty ones
@Firestorm01X2
Copy link
Collaborator

Firestorm01X2 commented Aug 2, 2021

I never seen before anyone complaned. Probably people get used to unstable releases for Cataclysm.

Obvsily it is somewhat messy, but it is not "true" releases - it is experimental releases after all.
Having release strategy will solve that. I mean normal release strategy with master, dev, version tags e.t.c.
nanohard actually pointed to that: #673

@scarf005
Copy link
Member

implemented in #3595.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants