- User Since
- Apr 18 2019, 7:59 AM (119 w, 6 d)
Pending CI refresh
Mon, Aug 2
For some reason, phabsend did not record the branch information (which was stable, according to Matt Harbison), so this went on default. It also shouldn't have landed on default at all since we're in a freeze, but the impact is minimal. I'll graft it to stable soon.
Even though it is quite simple, it can wait for the end of the freeze.
@valentin.gatienbaron We're supposed to have a real code freeze this cycle, so it's really the reviewers' job to ignore the patches that don't meet the stable criteria until the end of the freeze. As Martin said, it seems that some reviewers still queued patches.
I'll give other reviewers a little time to review as well, but this looks fine as a workaround. I hope we'll be able to figure out the underlying cause soon.
@pulkit I think this would be a good contender for stable and should go in during the freeze.
Mon, Jul 26
Thanks for the patches, they look like a good idea, however we're in a freeze right now so we'll take a look in August.
Fri, Jul 23
Thu, Jul 22
Should this go to stable or should it wait the end of the freeze? I'm not too sure.
I'm assuming both patches were intended for stable?
Does rhg still fail with this new mechanism? I'm assuming it does because nothing changed on its side, but we wouldn't want to lose the reproduction case.