Then, someone tests it out, and runs a special Meteor command meteor admin recommend-release which sets a flag in a database that that version is now “recommended”.
Essentially, we want to make sure we can test installing the build before it gets shipped to everyone.
So perhaps we can add something to automatically open a PR to the docs upgrading the submodule? We could maybe just do it when new tags are detected on meteor/meteor, or we could hook into the recommending process.
Thanks for taking the time to document this here. The master branch of meteor/meteor will always have the latest release included, and may show what’s coming in the next release as added value. Maybe just hyperlink to this source file from the docs to keep the complexity down.