At present we have continuous builds of ren-c as commits made which makes choosing a stable release difficult.
I’m suggesting we choose a core set of commonly used programs/utilities and test them against the new builds. If they all pass, then the new build becomes the candidate for the new stable release. If the tools fail, then they need to be amended until they work again before we decide on the new stable release. If they can’t be fixed, then we decide whether we can still use that tool.
For the first suggestion, I am suggesting that we chose existing module code as the corpus of code that we test against.
@rgchris Does that suit you since you’re the author of the most used modules!