Blog for Public Code

This blogpost


Subscription feed

Notes from the Standard for Public Code community call - 3 December 2020

Update from the Foundation



Rolling releases

We started this discussion because the Standard lacks guidance for ‘rolling release’ environments. We talked about codebases that deploy several times per day and how these could be referred to. We noted that the Standard doesn’t prescribe any specific version schemes.

We also talked about codebases that use A/B testing in production. Do they signal their maturity enough? Tests are usually already described in an issue, so they are at least somewhat documented. The important thing is that an outsider can understand what’s going on when they try to replicate the codebase. We didn’t come to a conclusion on exactly how the Standard could be updated with this, so we created an issue for future work.

Providing feedack

This discussion was based on the issue 349 (““Reviewers MUST provide feedback on all decisions” lacks clarity of intent”). We all agreed on that the most important feedback, and what the requirement should address, is for contributions that are not immediately accepted. During the call a pull request that clarified this was created.