Snapchat
Refactor Code to Use “Replica”
This tracks renaming any code still using the old master/slave terminology where back compat is not affected.
The older terminology is divisive and that’s not what KeyDB is about. On top of that “Replica” is simply a more descriptive name especially now that replicas can also push changes with Active Replication.
Hello @JohnSully, I am keen to give this a shot.
However, I noticed that the README refers to a CONTRIBUTING file, which I am unable to locate. Also, the documentation does not seem to talk about contributions, either.
What are the tests that the code changes need to pass? In the root of the repo, I see a series of 'runtest' files. Are they sufficient? Another thing I saw related to this was the ubuntu-test-latest GitHub Action. Is that the test I should be running?
./runtest and ./runtest-cluster are the two main ones.
Theres Snap internal CI that runs more, the public github CI is a bit limited because the free machines only have 2 cores.