I've got release duty today. I'm positive I wont s...
# development
e
I've got release duty today. I'm positive I wont start until after 2 PM US Pacific, but if you want to steer things, pile on.
👍 1
w
thanks John. there are 2.11.1 and 2.12.0 rcs too, but Eric and i have been expecting to do those this week, so i’ll do them.
e
I'm also seeing 2.8.1rc2, 2.9.2rc0 and 2.10.1rc1 - are we letting old rot or should these be un-neglected?
2.7.2 appears o be the last true stable release.
w
@enough-analyst-54434: the changes in 2.10.x at least are internal-only, and just intended to unblock future releases if needed
e
OK. And I can assume ditto for 2.8.x and 2.9.x?
w
you did the last pick to 2.9.x, and yea: it appears to be a similiar internal-only-to-unblock-future-actual-releases
e
Ok, this feels totally untenable, but I'll roll with it.
w
…ah, i’m missing that 2.10 and 2.9 both had rcs before those internal-only changes. so yea, we should likely release those. sorry, missed that bit.
@enough-analyst-54434: but yea: if you do the dev release, i’ll do branch releases. thanks again.
e
Yeah, my algorithm was just any branch w/o stable should be tended to. I stopped at 2.7.x since it was 1st that met the criteria. I dare not look earlier.
w
yea. exactly how far back to go has always been a question, and we should likely try to clear it up a bit. my line currently is likely 2.9.x, but not for any particular reason.
e
It looks like 2.8.1rc2 is the only release we've abandonded not on your list and not counting 1.30.5rc1. It would be good not to be abandoning any.
w
k, fine with me.