[BUG] Remove 2.20 before 3.0.0-alpha1 RC

[andrross]

Describe the bug

With no plan to release a 2.20 version, we need to remove the references from the code

There are a few related tasks here I believe:

• Remove 2.20 references from code
• Change bwc tests to run against the 2.19 branch instead of 2.x
• Reconcile CHANGELOG.md and CHANGELOG-3.0.md into a single changelog

Related component

Build

[dbwiddis]

How will this impact plugins who have already bumped to 2.20.0-SNAPSHOT per the automated build version bumps?

[mch2]

along these lines - 3.x is currently setting minimum_wire_compatibility_version to 2.20.0, preventing any rolling upgrade to 3.x. This should be 2.0.0

[peterzhuamazon]

Hi @mch2 @andrross any progress on this and is it a blocker for 3.0.0-alpha1?

Thanks.

[expani]

How will this impact plugins who have already bumped to 2.20.0-SNAPSHOT per the automated build version bumps?

@peterzhuamazon Do you have any idea on this ?

[andrross]

How will this impact plugins who have already bumped to 2.20.0-SNAPSHOT per the automated build version bumps?

@dbwiddis That version bump happened on the 2.x branch, right? Once we release 3.0 and then continue in maintenance mode on the 2.19 branch, then the 2.x branch will be removed/archived/abandoned as there is no plan for a 2.20 release.

[andrross]

along these lines - 3.x is currently setting minimum_wire_compatibility_version to 2.20.0, preventing any rolling upgrade to 3.x. This should be 2.0.0

@expani @mch2 I believe the minimum_wire_compatibility_version should be 2.19. The upgrade policy has always been to allow rolling upgrade from the latest minor of the previous major version, which is what the bwc tests are testing against.

[andrross]

Resolved by #17605

[peterzhuamazon]

Yes 2.20 is bumped on 2.x branch only and if there is no 2.20 anymore we will keep using 2.19 branch for patch releases.