In December 2015 MS introduced Current Branch (CB) method for SCCM too., like we have for Windows 10.
What it means to me ?
MS can deliver SCCM moving from longer release cycles to regular updates designed to support the faster way of updates for Windows 10 and Microsoft Intune and align with these products & features updates support as it is Business support application tool.
There is no Current Branch for Business (SCCM CBB) for SCCM, it's only SCCM Current Branch.
SCCM CB has Technical previews where it automatically appears in SCCM Console.
You can use these technical previews, however you can't degrade one version number to other. Typically, new versions of the technical preview are available each month In the admin console, new versions appear as “Configuration Manager Technical Preview YYMM.”
All these Feedback & new features will be bundled with upcoming SCCM 2016 version, So do not think that there is no 2016.... it will be release soon......
Are we talking similar to Microsoft update ? Even though I do not use Windows 10 in my infra I must have to update?
Yes, if you have SCCM CB, and it must go for regular updates regardless of you support it's supported products in your infra.
Each version is supported to 12 months. Each incremental update version may fix some security updated and include some new features, Where as SCCM 2012 / R2 (not Current Branch) versions will get only CU's to fix the security or bug fixes ( So ideally the CB update versions and CU's are same however CB are more frequent with some excited new features other wise both are same). Similarly windows 10 CB / CBB / LTSB will be supported if you update SCCM CB to N+1 and applications compatibility to N-1.
Tip of the Day................>
selfhost testing : The first recipients of builds are Microsoft employees who begin what Microsoft calls selfhost testing
