Minecraft-based version support policy #219
Unanswered
AugustinMauroy
asked this question in
Q&A
Replies: 1 comment
-
I don't want to have a bunch of branches for every Minecraft version. I would like to use tags when releasing a new Pumpkin version. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We need to think about how to manage the pumpkin semver and the Minecraft semver. In addition, we need to see how to support the different versions of mc.
Semver
For me you just need a Minecraft major for a pumkin major. And a minor/patch equals a minor pumkin. And patches are exclusively for pumkin.
Version support
For me, it would be necessary to have branches named
1.21.X
which is the version of MC. Then have a schedule that gives it Minecraft version support.The problem with a potential diary is that it will be on one branch, so if it is updated it will be out of date on the other branches. That's why the idea of an org can be useful in this case. There would be an
admin
repository, anothercore
repository and awebsite
repository for the docs which is independent of the code itself.Beta Was this translation helpful? Give feedback.
All reactions