I'm glad to see there will be a two week sprint to follow up on the missed one-week sprint rather than just missing it, but I don't like that you're pushing it out to til the end of the next quarter; it should be prioritized for the beginning of the next quarter since you're completely missing it (voluntarily) this quarter. That means you're going half a year without working on your core product. I remember a time when the core product was essentially the only thing the developers worked on, year-round.
Telling us this in the 11th hour is better than silence, but it makes it seem like y'all just forgot or made the announcement when someone complained (it's not like one can say Christmas and New Year's took you by surprise, since they happen at the same time every year).
There's also the underlying point of--you can always just run the sprint anyway and make people aware that because it's a holiday time, less work might be done. Or better yet, ask the community which they would prefer between a holiday sprint vs. a delayed but longer sprint to make up for it... that seems like a win-win: the community feels heard, and you either get what you planned (a two week sprint later) or you get away with doing less work than you normally would have to spend (due to holidays and downtime).
Full disclosure: because of the timing of the follow-up sprint and the 11th hour timing of this announcement, I gave this announcement a downvote.