Core team sync 2024-05-20

[madolson]

• Status of daily job (still failing?)
  • Pathway to green?
    • Should be fixed now, and we have a bot on the slack channel.
• Status of 1M QPS
  • Status of big endian hardware to test on
    • Kyle Davis will followup to get access to the hardware.
    • Open question about if pre-fetching is supported everywhere.
  • Target date
    • RC candiate for July
• Release cadence
  • Major release around the fall, minor release around the spring.
    • @madolson will documenent in valkey-doc
• Formating, Add clang-format configs #323
  • Should we commit to it?
    • Conceptually approved to as part of a CI Job
  • Summary of open questions:
    • braces around single lines? (if (x) return y;) -> No
    • BraceWrappingAfterControlStatementStyle MultiLine Never?
  • Developer setup
    • Create a Developer.md
    • Include IDE and environment setup @PingXie will own
• Inclusive wording
  • Update internal wording to remove slave/master
    • Yeah, start migrating internal code to use new terminology
    • NO BACKWARDS BREAKING CHANGES. Maybe identify all the cases.
  • Introduce aliases for master based configs
    • "masterauth" "masteruser"
  • Info fields and command returns should not get changed
  • Remove references to master in documentation
    • Where it's used in command APIs, document it's for compatibility.
• Propagating sharded pubsub messages in replication, Propagate sharded pubsub data via replication link #307
  • Should we optimize the clusterbus instead? or also?
    • "Or Also" was the decided path. Write an issue for it, then implement the replication.
  • Is it OK to return -MOVED for sharded pubsub?
    • Yes
  • How to communicate the capability?
    • We should implement the replconf version first, before merging this change.
  • How to avoid breaking change.
    • Shouldn't be marked as a write ACL category
  • Make regular pubsub an alias of sharded pubsub?
    • No
  • How obvious is the performance characteristics of pubsub in cluster mode
    • Create an issue indicating that we should add a warning in topics/pubsub
• Fork hiredis + hiredis-cluster as "libvalkey", fork hiredis-py?
  • https://github.com/orgs/valkey-io/discussions/511
  • Naming
    • Commit to libvalkey, for lack of a better name
  • "Protocol" name
    • Investigate coming up with a standardized name for "Redis" protocol.