premake / premake/premake-core

Improve & automate the release process

Open
#1,709 0 comments 0 reactions 1 assignee View on GitHub

@starkos is already working on this.

Since Sep 7, 2021.

enhancement
Dominant language
C
Stars
3.6k
Forks
654
Avg merge
1d 1h
Merged PRs (30d)
13

Description

What problem will this solve?

Right now, the release process is partially automated, but still requires several manual steps (which I mess up on a semi-regular basis) and a local install of all target platforms. Before we get to stable I'd really like to see this process fully automated and ideally leveraging GitHub's build systems so that any of the core developers can push a release when needed.

Once automated, it might be possible to start pushing nightly builds again as well.

What might be a solution?

GitHub actions (waves hands) something something. More research is needed to figure out the best way to do this, and how much of the process can really be automated.

What other alternatives have you already considered?

I've been muddling along with our current hybrid approach but it isn't working that great, and kind of relies on me to stick around to keep doing it.

Anything else we should know?

Nope.

(You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.