It’s been over two and a half years since 0.C, and there are still plenty of open issues on 0.D’s milestone on GitHub. If the devs actually want to get 0.D done at some point, wouldn’t it make sense to implement a new feature freeze and only accept PRs for bug fixes until 0.D is ready to go?
In short, no.
It’s not reasonable to start a feature freeze until that list of issues is small enough that the feature freeze will be short, say less than a month.
If it takes longer than a month or so, we’d more likely start losing developer interest than encourage extra effort on the part of developers.
If we had enough manpower one the merge side of things, we could fork into a stable and development branch, merging only bugfixes to the stable branch, and features and bugfixes to both. However that is precisely what we are short of, so it doesn’t help.
1 Like