FlatBuffers 3.0.0 tracking issue

[aardappel]

This is the tracking issue for the release after 2.0 (see https://github.com/google/flatbuffers/issues/6353).

Please link from issues that should be resolved by the next release to this issue.

Any other release related discussion welcome here too, but for extensive discussion of some aspect of it please create new issues.

[aardappel]

@krojew made me aware there is actually a github feature for tracking releases: milestones.

It is here: https://github.com/google/flatbuffers/milestone/1

You can add issues/PRs to it directly.. this issue for general discussion of the release.

[dbaileychess]

Should we close this issue then?

[krojew]

It might be good for tracking release status for various languages. For example, I have no idea which languages have not been updated to 2.0.0 at the moment without such list.

[aardappel]

Yes, milestones have no associated discussion so let's leave this open. But no need to link issues here anymore, just use the milestone.

[dbaileychess]

Ok, I linked this to the milestone.

[github-actions[bot]]

This issue is stale because it has been open 6 months with no activity. Please comment or this will be closed in 14 days.

[aardappel]

not-stale

[CasperN]

I'd like to make this issue a release tracker for 3.0.0 specifically, since there are some breaking changes planned for Rust APIs (#7103). It did take a few months to plan and execute last time, so perhaps we should start the discussion

[CasperN]

@mustiikhalil found in #7269 that its possible for a type that doesn't have a (private) annotation to contain a type that does have such an annotation, effectively leaking the inner type to the world (and causing errors with the rather picky rust compiler). Before 3.0 we should change the --no-leak-private-annotation flag to --allow-leak-private-annotation and force users to migrate.