Won't comment directly on the compatibility window (although I lean toward the status quo and just requiring upgrades from the latest patch version of a major release), but I think I've also arrived at a point where I'm not convinced running the Python upgrade tests pre-commit is an efficient use of resources. It's not just the hardware required, but the fact that we have to expend mental energy to glance over the couple flaky upgrade tests that have nothing to do with our patch, etc.
- Re: [DISCUSS] 5.1 should be 6.0 Jeremiah Jordan
- Re: [DISCUSS] 5.1 should be 6.0 Jon Haddad
- Re: [DISCUSS] 5.1 should be 6.0 Benedict
- Re: [DISCUSS] 5.1 should be 6.0 Mick Semb Wever
- Re: [DISCUSS] 5.1 should be 6.0 Jordan West
- Re: [DISCUSS] 5.1 should be 6.0 Benedict
- Re: [DISCUSS] 5.1 should be 6.0 Mick Semb Wever
- Re: [DISCUSS] 5.1 should be 6.0 Josh McKenzie
- Re: [DISCUSS] 5.1 should be 6.0 Benedict
- Re: [DISCUSS] 5.1 should be 6.0 Josh McKenzie
- Re: [DISCUSS] 5.1 should be 6.0 Caleb Rackliffe
- Re: [DISCUSS] 5.1 should be 6.0 Benedict
- Re: [DISCUSS] 5.1 should be 6.0 David Capwell
- Re: [DISCUSS] 5.1 should be 6.0 Josh McKenzie
- Re: [DISCUSS] 5.1 should be 6.0 Benedict
- Re: [DISCUSS] 5.1 should be 6.0 Josh McKenzie
- Re: [DISCUSS] 5.1 should be 6.0 Jeremiah Jordan
- Re: [DISCUSS] 5.1 should be 6.0 Josh McKenzie
- Re: [DISCUSS] 5.1 should be 6.0 Jeremiah Jordan
- Re: [DISCUSS] 5.1 should be 6.0 Jon Haddad
- Re: [DISCUSS] 5.1 should be 6.0 Mick Semb Wever