[C#] Schema should be optional on FlightInfo

[ndglover]

Describe the enhancement requested

Similar to 37553

The idea being that the Schema is not a required field for FlightInfo. The Schema can be sent as part of the messages in the subsequent request.

Component(s)

C#

[CurtHagenlocher]

Issue resolved by pull request 43673
#43673

[acceleanu]

Is it possible to have a release candidate for this fix?

[CurtHagenlocher]

Is it possible to have a release candidate for this fix?

There's no existing process by which prereleases get published to nuget.org, so if you need something before the final 18.0.0 release you'd need to build it yourself from source.

[ndglover]

@CurtHagenlocher do you have a date for the 18.0.0 release?

[CurtHagenlocher]

Code freeze is at the end of September and the release will be sometime during October. We can't really predict a date because it depends in part on how the testing goes.

[ndglover]

Is there a reason not to have release candidates before that final release? It would seem to make sense from a stability perspective and also from an end user perspective. Waiting at worse case an entire quarter seems sub-optimal and each person then needs to fork the repo and manage builds etc

Happy to make a contribution if that's a good idea but not sure what would be involved.

[CurtHagenlocher]

Yes, there are absolutely one or more official release candidates that are used for testing. I believe these would even be signed, if that's an issue. They are not, however, published to nuget.org. As I understand it, doing so would likely be a significant process change because I think the release candidates are exactly that: something that will be released and published if testing is successful -- versus artifacts that have been explicitly marked as non-release.