aminghadersohi commented on PR #44288:
URL: https://github.com/apache/superset/pull/44288#issuecomment-5685584723

   Maintainer review / landing coordination: @eschutho (requested reviewer and 
#44283 author), @mikebridge and @richardfogaca (#44317 author/reviewer), could 
you confirm which baseline repair should land?
   
   #44288 at `d6f00dcffec9beb74bc9480b40f38515c5527a5a` has all 13 required 
checks SUCCESS; the [full 84-check 
audit](https://github.com/apache/superset/pull/44288#issuecomment-5685556322) 
has no failed/pending checks. The #44285 owner reports all 15 failures audited: 
12 startup jobs blocked by the two master Alembic heads and three dependent 
gates. Other driver PR owners have reported the same blocker.
   
   #44317 is another no-op merge of these exact parents, with revision 
`e2f0a912492a`, and GitHub reports APPROVED (the recorded approval is on its 
earlier commit). #44283 also joins these parents inside its ClickHouse 
migration. Please select only one repair:
   - If #44288 lands, reparent #44283 onto `e2f3a1b9c640` and reassess/drop 
#44317.
   - If #44317 lands, reparent #44283 onto `e2f0a912492a` and reassess/drop 
#44288.
   - If #44283 lands first, reassess both standalone repairs.
   
   Landing parallel merge revisions unchanged recreates multiple heads. No 
consent, approval of the latest #44317 SHA, or landing decision is assumed. I 
will notify the #44285 owner only after verifying the selected repair is 
actually on master; they will then rebase and rerun all applicable CI. No merge 
or draft conversion will be performed by this session.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to