anton-vinogradov opened a new pull request, #13863:
URL: https://github.com/apache/ignite/pull/13863

   Changes to Ignite's public contracts need an approved RFC. This check flags 
PRs that touch known contract paths. It asks for an RFC or a decision from a 
reviewer with write access on the current PR commit. A later implementation PR 
can refer to an RFC already on master.
   
   For new and amended proposals, the check reads the vote and result on dev@, 
checks the voting period and compares the voted RFC with the file in the PR. It 
supports three committer votes or announced approval after seven days without 
objections for compatible additions. Ambiguous mail or voter identities need a 
reviewer to verify the evidence.
   
   This is a follow-up to #13760 and 
[IGNITE-29220](https://issues.apache.org/jira/browse/IGNITE-29220). After both 
PRs merge, set the Actions variable `IGNITE_RFC_CHECK` to `true`, exercise the 
check on master-targeting PRs, then require `RFC process` for merge. Setup, 
reviewer decisions and recovery are documented in `.github/RFC-check.md`.
   
   Validation: 42 unit tests passed and actionlint checked both workflows. 
Replayed two public Ignite votes to check early closure and list-rewritten 
voter addresses.
   


-- 
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]

Reply via email to