@masagi, I think that’s probably a good practice. I personally prefer to wait a while before updating my live sites.
In my experience when WC releases a 2.x update, it will soon be followed by a number of 2.x.x updates to resolve issues that get reported.
This is to be expected. They have loads of users using a wide variety of different combinations of plugins, themes, etc. It can take a few minor updates after a large update to get things smoothed out. It also takes time for theme/plugin developers to get their own stuff compatible with new WC updates.
I like to wait until the minor updates slow down after the big update. For example, 2.4 was released. Very shortly after that 2.4.1 was released, and then not long after that 2.4.2 was released. I wouldn’t be surprised to see a 2.4.3, 2.4.4, etc.
Once those minor updates stop coming so quickly it’s generally a good time to go ahead and update, but even then it’s recommended to replicate your live site on a test server so you can update there first and run tests to ensure everything is ready to rock.
Just my two cents.
