Just a side note / opinion:
I think both you are ok!
1st) Last week I was upgrading my dozens of test DBs here and thanks to that RED warning in the frontpage, I was able to see clearly when I had cvs updated some places incorrectly. I think it was ok for crazy-early-compulsive adopters like me.
2nd) Agree that, after 2-3 weeks from branch point, the RED warning can be moved to the notifications page, exactly like has been done. Perhaps I'd had kept it a bit more but it doesn't matter.
3rd) We should try to branch before release always in the future. I think 2.0 was an (ok) exception to that (tons of changes, switching from cvs to git...). But I think we should make the "branch-before-release" a requirement from now. It's better for everybody (devs can continue on master, admins clearly know were the stuff is...), but for the fact of double-pulls. And that isn't a big problem as far as we are used to it.
PS: Testing it right now...