If you’re like me, you look forward to all the even numbered months. Not just because of Valentine’s Day and my dad’s birthday, but because that’s when our beloved SharePoint gets its new Cumulative Updates. The odd numbered months just don’t feel like as much fun in comparison. I felt bad for them.
Until today… (well, yesterday)
I was surprised two days ago when SharePoint 2013 got a July CU. July? That’s an odd month, this makes no sense! This changes everything. Is water still wet? Is the sky still blue? I can’t keep up!
Yesterday Microsoft announced that SharePoint on-premises, both 2010 and 2013, will start getting monthly CUs. That’s going to be a lot to keep track of, but I think I’m up to it. I will still maintain my SharePoint 2010 Builds page and my SharePoint 2013 Builds page. My guidance on CUs hasn’t changed. You shouldn’t install a CU unless it contains a fix that you need. And if you talk yourself into installing a CU, install it in a test environment first to see if it breaks anything. I maintain a wiki with a page for every patch. As soon as I know about a problem with a patch I’ll record it there. If you do find a problem with a patch, let me know and I’ll add it.
At first blush, I think this is a good thing. Like SharePoint Online, Microsoft seems committed to updating SharePoint on-prem at a rapid pace. The good news with on-prem SharePoint is that we get to choose whether the patches get installed or not. Seems like the best of both worlds to me.