@onur_can - there is a difference in some operating systems that makes it wise to delay IF POSSIBLE.
For example, in OpenVMS you NEVER ran version x.0 because it contained new features. Those new features were buggy. Version x.1 cleaned up those versions. With the Navy, we had a mandate to use the latest version of the O/S available - but our "out" was that if our system was deemed mission-critical then we had to schedule down-time. AND we had enough products that the upper echelons decided it was OK to accumulate a few versions and have one great big "update the world" weekend.
You HAVE to know that the first version of Windows NT was buggy as all heck but once a few patches became available, it stabilized quickly. Trust me when I say that there is not - and perhaps should NEVER be - a rush to install the latest, greatest version of any O/S precisely because it might be the latest, greatest MESS that ever hit the fan. Take the furor over Win10 release 2004, which "reset" a whole bunch of my settings and forced me to find my notes on where I could turn off this or that feature. Not to mention pushing O365 and Edge again, neither of which are of any value to me. I'm NEVER hot to install new software that counts as a "major feature release."
Do you know WHY it is that way? If you don't, you need to know it. The best software regression testers are the customers in the field. The testers in the software companies think too logically. They think like computer people. They don't think like "average Joe Schmuckatelli." Here's a case in point. We had a "rock-solid" system that was going to be responsible for interstate transport of hazardous material (petroleum distillates) through pipelines. Minimum down-time required. We were sure we had it right. So the customer comes one day for progress testing to verify that we are in fact working on his machine. He walks over to our setup, hears our spiel about how solid we think it is. He walks to the operator console using our special keyboards. He sits down on the operator's special keyboard. And lo and behold, 8.02 seconds later the system crashes. That is because those of us in the industry can't think down to the level of the minimum wage system operators who often get put on the "graveyard shift." That is why version x.0 of something isn't such a great idea all of the time.