> > > > ci-cassandra.a.o needs to be our canonical CI > > it's the only one fully usable by a volunteer based > > > only green in both counts as green > > I think today might just be my day to annoy you Mick. :D Sorry! >
On the day I'm laid up in bed with a cold. Go for gold :-) I think this is contradictory. We can't require circle to be green for a > release if the free tier usage of it a) doesn't pass tests, and/or b) > requires a license incompatible w/some contributors. That effectively would > make circle + asf ci our canonical ci, right? > That's taking it out (or twisting) my context a bit, let me explain… First, I did not mean the free tier. It is not usable AFAIK. It could be updated so it was constrained in what it could run and was stable, but then it's not complete so there's limited value here. IMHO plugging in GitHub Actions to do a very basic build+test would hit a larger newcomer audience. Second, I didn't mean one *had* to run both. Just like post-commit will catch things, just so long as that breakage comes around to you and you accept your involvement in it. We (the whole community) need to help out when the author cannot reproduce/debug the failure, and this isn't just limited to premium circleci. less flakies than the previous release > > This statement makes me wary. :) Why not "no test failures"? > More than happy to go for that. And I damn hope we are there for our next major release. This statement was more just a preference to lean on the more pragmatic side. We know our north star, keep moving towards it.
