Overall tracking issue for breaking changes in 3.0

[ajcvickers]

The first place to look for information on breaking changes is in the breaking changes page maintained in the documentation.

At the issue level, breaking changes are tracked using the breaking-change label.

Breaking change issues break down for 3.0:

• Breaking changes currently planned to be fixed for EF Core 3.0
  • Please note that this is not a guarantee that the issue will be fixed in the 3.0 release. Re-evaluation of the plan throughout the release cycle sometimes results in issues being pushed out to a later release.
• Breaking changes fixed for EF Core 3.0 but not yet shipped
• Breaking changes fixed in EF Core 3.0-preview4
• Breaking changes fixed in EF Core 3.0-preview3
• Breaking changes fixed in EF Core 3.0-preview2

[popcatalin81]

Please consider fixing #7089 as part of breaking changes. This was one of the most controversial features of EF core needs revisiting. Needing to have a nullable boolean (tristate), where only two values are needed at the application level is not ideal.

[ajcvickers]

@popcatalin81 We plan to support the pattern shown in #15182. This allows two values to be used at the application level, while still allowing the store-generated value to be used when no value was explicitly set. I believe all other cases are covered by appropriate configuration. (That is, either not configuring a store-generated value, or configuring it only for migrations and not using at update time, possibly coupled with moving the default to the client code.)