Skip to content

Document the preferred Luanti release schedule #228

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Document the preferred Luanti release schedule #228

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 17 additions & 2 deletions content/for-engine-devs/releasing-luanti.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,15 @@ aliases:

# Releasing Luanti

The [feature freeze](#feature-freeze) and release date is set by core developers.

Historically, the Minetest release intervals were in between half and an entire year. To deliver bugfixes and features more quickly, the goal is to release more often.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Historically, the Minetest release intervals were in between half and an entire year. To deliver bugfixes and features more quickly, the goal is to release more often.
Historically, the Luanti release intervals were in between half and an entire year. To deliver bugfixes and features more quickly, the goal is to release more often.

we want to call it Luanti, even if it was called Minetest back then, to minimize confusion. can also do "Luanti (then Minetest)" if you think this is important.

Copy link
Member Author

@SmallJoker SmallJoker May 8, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might Minetest/Luanti be okay too? I explicitly used this notation because it predates the whole rename action. I wonder whether Luanti (then Minetest) is generally understood - as I am not a native English speaker.


* Goal: January, April, July, October
* A release before November should be prioritized because the Game Jam ([2024 forum post](https://forum.luanti.org/viewtopic.php?t=31059)) would like to make use of new features.

Patch releases are exempted from this schedule.

## Checklist

```
Expand Down Expand Up @@ -41,9 +50,15 @@ aliases:

### Announce a feature freeze

(_Skip for patch releases_) Usually, a **feature freeze for one week is announced in #luanti-dev**. New features aren't accepted in this time and people focus on finding and fixing bugs. To find high priority issues faster, consider linking a release candidate binary to get more test results. This release candidate is usually also posted on the forums (News section).
(_Skip for patch releases_)

New features aren't accepted in this time and people focus on finding and fixing bugs.

The feature freeze and release date is set by core developers.
1. Move all open feature PRs of the current [milestone](https://github.com/luanti-org/luanti/milestones) to the next one.
2. Announce the **feature freeze in /topic of [#luanti-dev](/about/irc)**.
3. Post the release candidate builds on the forums ([News section](https://forum.luanti.org/viewforum.php?f=18)) and (optional) as pre-release on GitHub ([Releases page](https://github.com/luanti-org/luanti/releases)).
* This helps to find high priority issues faster.
* You may use the buildbot/CI artifacts from `master`. If needed: do provide manual signing instructions for the MacOS and Android builds.

### Autogenerate files

Expand Down