11-20-2015, 03:02 PM
(This post was last modified: 11-20-2015, 03:05 PM by LogicParrot.)
So far, there has been at least two incidents of people getting issues thanks to using the "testing" branch:
1. https://forum.cuberite.org/showthread.php?tid=2205
2. https://forum.cuberite.org/showthread.php?tid=2182
This is an indicator of what we all know - the testing branch is too old, and is in fact less stable than master.
I think we should roll out a new testing.
To avoid being stuck in this loop forever, two things must be done:
1. The mistake of keeping "testing" around too long without graduating it into release should not be repeated. Higher priority should be assigned to fixing crashes than introducing features.
2. In Github, not every crash bug should automatically be tagged with the "testing" milestone. Instead, that should be done only after it is confirmed that the bug was not actually introduced in the "master" branch. Tagging all crashes with "important" makes sense though.
1. https://forum.cuberite.org/showthread.php?tid=2205
2. https://forum.cuberite.org/showthread.php?tid=2182
This is an indicator of what we all know - the testing branch is too old, and is in fact less stable than master.
I think we should roll out a new testing.
To avoid being stuck in this loop forever, two things must be done:
1. The mistake of keeping "testing" around too long without graduating it into release should not be repeated. Higher priority should be assigned to fixing crashes than introducing features.
2. In Github, not every crash bug should automatically be tagged with the "testing" milestone. Instead, that should be done only after it is confirmed that the bug was not actually introduced in the "master" branch. Tagging all crashes with "important" makes sense though.