Old releases support

[scagood]

I have been thinking about our old releases, and I was wondering if we should:

1. Add EOLs to old plugin versions.
   For example, 180 days after the next major version
2. Change the branch names to match the major version
   For example, master -> 17.x, 16.x, and so on.
3. Releases
   All releases should be very simple to publish via version control, to that end I think that release please should be configured with a target branch for each supported major version
4. Renovate
   I was wondering if we should configure renovate for old release branches too?

[aladdin-add]

I'm open to 1, 3. all development should be on the main branch, and given the cost of maintenance, we will only back port important bugfixes or security fixes to previous branches. So, it doesn't seem too worthwhile to spend too much effort on the previous release branch.

re 2: do you mean renaming master -> 17.x. we will need to change the default branch to 17.x, 18.x... it sounds not a good idea. 😅

[scagood]

👍 That makes sense to me, lets drop 2

[scagood]

Okay, so I think these are the action points:

• Add a "Support" section to the README.md
• Configure Release Please on the v16 branch
• Configure Renovate on the v16 branch