Fixes for 7.0.0

[philipphofmann]

This is an informal place to collect things to improve or fix for the major version, that are breaking changes. Once we start with the next major version we are going to create issues for them.

[philipphofmann]

Fixed with #939

[philipphofmann]

See #975

[philipphofmann]

See #1017

[philipphofmann]

Protocols for Client, Hub, and Transport.

[philipphofmann]

Also add startSession and endSession when removing the currentHub, see getsentry/develop#248

[philipphofmann]

Add a thread-safe implementation of a dictionary to expose the dict instead of having methods as setTag and removeTag, for example, on the Scope or SpanContext.

[bruno-garcia]

We don't want to expose a Map to users though right? In most SDks Sentry doesn't even let user read the scope. The more API surface we add here the harder to evolve it becomes (like synchronizing the scope on change for example).

[bruno-garcia]

Not against it but might be that we just keep that internal. On Java for example it seems we return the actual reference to the dictionary so users can do spanContext.getTags().whateverMapClassExposes.. hold that reference as a field or whatever. It's just very leaky. Ideally it would be a readonly interface or just returns a key/value iterator

[philipphofmann]

Yes, I agree making it readonly makes sense.

[philipphofmann]

See #1026

[philipphofmann]

Use a class for mechanism metadata instead of a Dictionary on SentryMechanism. Also, move SentryNSError to this class.

[philipphofmann]

See #1038

[philipphofmann]

7.0.0 is out now. Put the fixes for the next major in 8.0.0.

[armcknight]

And also 8.0.0 is out now, so that discussion is also now closed. See the new one for 9.0.0!