Define a support time-frame for v7 and v8

[lforst]

Description

We should define and document a time-frame of which we will support v7 and v8 and which kind of support we will deliver:

• Security?
• Bugs?
• Features?

[mydea]

First idea:

• v7: Bug fix support until release of v9. Critical bug fixes may be backported afterwards, but no more guarantees apply.
• v8: Bug fix support for 6-9 months from release of v9 onwards

[lforst]

I came up with maybe the following when v9 ships:

- **v8**:
  - Security patches for 12 months or until the next major, whichever comes later.
  - Bug fixes for 4 months.
  - Feature updates based on demand and feasibility but no guarantees.
- **v7**:
  - Critical bug and security patches may be backported but no guarantees.
  - Support for this version has officially ended.
- **Older Versions**:
  - Support has ended.

[lforst]

We talked about it a bit internally. We as a team feel like it's a bit stressful to have these support time-frames - not as a developer of the SDK but as a user.

As someone who has worked on the SDK a bit, I can confidently say, that if there are any super annoying bugs, or papercuts that someone would like to have fixed, we will backport them in any case as long as the demand is reasonable.

The standard we hold ourselves to when tackling security issues is also high enough that we will also most definitely backport security fixes.

For these reasons, we will most likely not define a support time-frame. Users should expect to receive support when their concerns or issues are reasonable. We will decide on a case-by-case basis what makes sense to backport and fix.

[lforst]

Settled on this:

https://github.com/getsentry/sentry-javascript/blob/70cae500d72f23f26f60bb14b692ea0b26513d17/MIGRATION.md?plain=1#L161-L169