Scott Kurtzeborn

> Need to find a way to run coverage gates if and only if coverage information is available. @danieljurek, agreed. Seems like a conditioning fix in the pipeline.

Bumping this back to use the "Client" label instead of "EngSys" because these labels are used to track _who_ is doing the work and not the area the issue occurs...

The "sync-eng" branches will get cleaned up automatically (and at the time of this comment there were only 3 of those). However, @danieljurek, you have 7 branches open on this...

Labeling this one "Client" since this is about finding a solution for C. Agreed it's possible the shared test proxy service may be a solution here.

@danieljurek has provided swag of 5 days for this work. Since he's on leave, I'm leaving this assigned to you @RickWinter. My understanding is that this will not be release...

@ahsonkhan, what scenarios are you releasing out of a feature branch that would require the version in main to be bumped? Feature versions should already be at a higher preview...

@ahsonkhan, you might consider what we do in .NET as a guide in how you add support for release and debug here. In .NET all PR validation builds and validates...

We do not currently have any perf tests for iOS client libraries. When we do (or to help get started on them) please reach out to @mikeharder so we can...

I've closed the duplicate issue. Copying over this comment from that issue: > Assigning this back to the client team for follow up. The infrastructure is all in place for...

We don't have any client performance tests to run in android yet. When we do (or to get started) please work with @mikeharder to get them integrated into our release...