Document the preferred Luanti release schedule #228
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SmallJoker
force-pushed
the
pr_228_document_release_schedule
branch
from
f422a6a to
5951916
Compare
appgurueu
reviewed
May 5, 2025
| @@ -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. | |||
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the PR version for #225.
To properly document the process, I found that rewriting the "feature freeze" section helps to convey the intend of releasing more often (skip over PRs that would otherwise stall the release).
Feel free to provide suggestions.