I do not mind em actually if they patch some major. Issue like the exploits some recent ransomwares used i am installing it asap when the updates are to no big interest to me i keep postponing it for few days till i give up and letting it update 😛

What's really nice about the Win10 model moving ahead is that according to Microsoft there won't be anymore full ISO upgrades--the new builds will come in Cumulative Updates, instead. I think that's great, so long as Microsoft actually sticks to that, of course. I like it because it indicates that the basic core of Win10 is stabilizing and reaching maturity, at long last. In the Win10 Insider's program, I updated to v1909 from 1903 in a CU (or maybe two CU's)--much better than the ISO upgrades--faster and cleaner, too. After five years in the "fast ring"--updating 1-3 builds per month via ISO, I got tired of it finally and dropped down to the "Release Preview ring", which means I'll only update when the next version is ready for Release Preview--then stay on that version until the next RP build, and so on. Right now, I think that v1909 build 18363.535 is the best build of Win10 to roll out yet, and by a decent margin, too. I really like the fact that I can still participate in the Win10 Insider's thing while sitting on 18363 for a nice long while...

That is not what has been said by microsoft at all, infact its the opposite. There are no plans to do future service updates like 1909.

Wasn't that one just to have a 19H2 build but then not really as it's 19H1 with a cumulative and a tiny little "enablement" package that just swapped 18362 to 18363 with the same cumulative data. Though it's interesting to see that 20H1 and 20H2 are actually a thing after the former info on how it was moving to a yearly release cycle but then 20H1 was already in development so it doesn't have to be a immediate change either. EDIT: Fulfilling the obligation for a 19H2 type OS update and full build even if it's basically a cumulative update with some features added to it or backported. (And a one time thing I suspect.)

the 1909 update has been confirmed by the azure team (which windows is now under) to line up the service update releases with december(march)

JonasBeckman:

Wasn't that one just to have a 19H2 build but then not really as it's 19H1 with a cumulative and a tiny little "enablement" package that just swapped 18362 to 18363 with the same cumulative data. Though it's interesting to see that 20H1 and 20H2 are actually a thing after the former info on how it was moving to a yearly release cycle but then 20H1 was already in development so it doesn't have to be a immediate change either. EDIT: Fulfilling the obligation for a 19H2 type OS update and full build even if it's basically a cumulative update with some features added to it or backported. (And a one time thing I suspect.)

Could be. Size and scope of updates should never be taken for granted, as 19h2 has shown. In terms of features, they are not obligated to come up with any with every release.