+1 Haonan
> On Sep 8, 2021, at 5:12 PM, Christofer Dutz <[email protected]> wrote: > > Hi all, > > I just wanted to share my observation regarding the way releases are being > done here. > > Initially I validated every RC I could. Being your mentor, this was sort of > my job anyway. > > This changed when we started cutting a lot of release candidates. I had > reviewed a lot of RCs that were cancelled shortly after I did the review. > > I don't know how others do their reviews, but if I do that it takes time > (usually more than an hour), as I manually check a lot of things. Whenever a > RC was cancelled as someone had a "little fix" he "needed" in the release, it > was invalidating all of that work and I had to do it over and over again. > > So in the end I stopped validating releases ... waiting to see if again a RC > is going to be cancelled and only to start doing my PMC duty on the last > minute. Mostly however I missed that last minute and the release was cut > without me validating it. > > I just want to make you folks aware of the fact that you are releasing in > pretty quick cycles anyway ... how about releasing things and simply > accepting that a fix will be in the next version? Ok ... if something really > is preventing someone from using the release, it should be fixed, but then I > would instead propose to have measures in place to not cut a release on a > not-usable version. > > Cause the way things are currently handled, I don't see me voting much in the > near future. > > Chris > >
