I found a (IMO) medium critical bug in the to-be-released RViz 1.14.22: After PR #1808: Segfault when loading RViz config with RobotModel display using non-default parameter name · Issue #1825 · ros-visualization/rviz · GitHub .
It will lead to segfaults for users with stored RViz configs that use a RobotModel display configured to use a non-default parameter name while also specifying another model on /robot_description ROS parameter.
Not sure if this is something the release should be held off for. In some of our use-cases, we have this configuration (i.e. multiple robot models on multiple parameters with one of them being the default /robot_description).