 In order for
a feature to be considered "ready" at this stage, it must be ready as-is
with no blockers. Features are a no-go even if they are close and
additional work on the beta branch would make it ready.</p>
<p>Because this process happens every six weeks, there will be another
opportunity for a feature to make it soon enough.</p>
<p>Once this is done, the master branch is merged into beta. A
<code>features.json</code> file is added with the features that are ready.</p>
</section>
<h3 id="toc_beta-rele