Publishing of images for 7.0.2xx SDK feature band deferred until March release

[mthalman]

Publishing of images for 7.0.2xx SDK feature band deferred until March release

As part of the release of version 7.0.200 of the .NET SDK, a breaking change was introduced that was related to the use of the --output option in the build command. Based on customer feedback, this breaking change will be mitigated in the 7.0.201 SDK release in March.

While we normally publish the latest SDK feature band for the SDK container images, we haven't yet done that for the 7.0.2xx feature band. So if you're using any of the latest versions of 7.0 SDK images, you're actually getting version 7.0.103. Based on this breaking change and the plan to mitigate it, we've decided to defer updating to the latest 7.0.2xx feature band until the 7.0.201 version is released in March.

You may wonder why we can't just publish both feature band versions and keep the floating 7.0 tag pointing to the 7.0.103 version until March. In order to ensure the operational costs for our container images are kept low, we only publish the latest SDK feature band for each .NET version and so all of our infrastructure is predicated on that assumption. This is why it's not a simple matter to publish both feature band versions.

We understand that there is a desire to have the latest 7.0.200 version, as requested in #4423. Many are unlikely to be affected by this breaking change. But we've decided it's best to avoid flowing this breaking change until it's appropriately mitigated.

[mthalman]

The 7.0.201 SDK was released early and so new SDK images have been published for this version. See #4460.