Skip to main content

In the latest release (July 27), I counted twelve changes/features that were delayed until an “independent” release on August 24.

Why?

I think it’s a bit challenging to mentally keep up with what was changed vs. what’s delayed.

I’m really curious about the purpose of delaying those a whole month - why not just delay the whole release? I know other admins are curious as well.

 

We’ve been discussing this as a team as well @darkknight. To answer your specific question, there are quite a few features that many customers are eagerly awaiting which were not going to be ready for the July release. We did not want to delay getting those features into the hands of customers by a whole quarter. And in some cases like certain engineering or infrastructure efforts, it is not possible to release on the same day as the quarterly release so there are times where an independent release is a necessity. 

All that said, we are going to move away from independent CS releases wherever possible in the future to avoid these types of challenges. 


Reply