Can we not write in 8.9 notes that upgrades to 9.0 may work but is not officially supported, and that they should wait for 9.1. Then add 8.9 back compact tests to 9.1. Am I missing something?
Jan Høydahl > 16. jan. 2021 kl. 18:43 skrev Adrien Grand <jpou...@gmail.com>: > > >> On Thu, Jan 14, 2021 at 8:02 PM David Smiley <dsmi...@apache.org> wrote: > >> I'm not familiar with why the testing needs to be manual instead of >> automated. After having a RC of 8.9, couldn't we add the back-compat >> indices to branch_9x and check that 9.0 is happy with them (running >> applicable automated tests) as a precondition for releasing 8.9? >> Regardless, you say we've done it before, and we can do it again. I think >> it's likely it'll happen. > > > Right, this is what needs to be done (though ideally on 9.x tags rather than > branch_9x). I called it manual because it requires special action and is > neither checked by Jenkins nor by any of the people who run the smoke tester > on release artifacts. My personal take on this is that the risk of having a > backward compatibility gap or the cost of investing into automated testing > for this outweigh the benefits we can get from releasing new minors of the > previous major. I couldn't attend this meeting, what is the motivation for > keeping releasing 8.x after 9.0 is out? > > For the record, I am less worried about patch releases, which have much > smaller scopes and never change file formats. So I'd be fine with doing > 8.lastest patch releases after 9.0 is out, similarly to how we released 7.7.3 > after 8.0. > > -- > Adrien
