I've created a 2.1 maintenance branch off of main. If more release candidates are needed, we can create them from there. That allows us to move the main branch forward for the next version without impacting 2.1. I expect the next release to be a 3.0 non-LTM, because we have a lot of cruft to remove that is breaking API changes, and it'd be good to do that prior to adding new 3.x features.
Christopher
