Since Lasse left the project there is nobody who has the same level of commitment and competency to fill his former role in the project yet. Still, the community has not stopped contributing to the project, albeit at much slower pace and (some might say) in lower quality. In the past it was also Lasse who assessed the readiness of the master branch before tagging it for release. So now I would like propose a change to make the quality of release becomes the responsibility of the community itself. English is not my primary language, so I hope I get my points across correctly.
The change should actually bring Urho3D project closer to other OSS project doing the releases. Instead of tagging the master branch when it is deemed ready, it will be tagged as often as possible. The postfix of the tag (’-ALPHA’ or '-BETA or ‘-RC’) or the absence of it will indicate the maturity of the tags. In other words, do not expect future tags to always work out of the box for you, but instead you are encouraged to test out the tags against your own use case and platform, and send back bug fixes as PR timely if you want them to get fixed and incorporated in the next release. On the maintainer side, this tagging often does not actually add any significant work because our release/tagging deployment mechanism is already fully scripted/automated. And since the maintainers will be freed from the burden for the quality assurance, we would not hesitate to “click the button” for tagging more often than in the past. In the end of the day it is the responsibility of ALL to get the release right.
Some of you do not want to build on top a moving ground and avoid master branch. I have observed the download stats for release tag is always higher than the snapshot on any release (not just 1.7). So having a pre-release tag should hopefully address the concerns of these peoples. Getting the tags constantly push out should also give the impression that the project is still alive and hopefully that could attract a right person to fill the vacancy.