Weekly meeting Notes

Valkey Meeting notes

Format and introduction

Notes will take the form of:

1. Top level topic
   1. Discussion point 1
      1. Comment about discussion point 1
   2. Discussion point 2
      1. Comment about discussion point 2
2. Top level topic ...

Core team syncs

Core team syncs happen every Monday at 14:00 UTC. Given the geographic distribution of the team, we are trying to keep the attendance small and we are currently not publishing a public invite. The meetings is open to those that have a topic to discuss though, simply add a request to discuss it in an issue and we will get you the invite.

Next agenda

If you are an active contributor and on the invite, you can add items here to be discussed in the next invite.

Past meetings

rd.

Core team sync 2024-09-02

• Valkey 8.0.0-rc2
  • Release postponed due to CI failures
    • Discussion about failing testcases
    • Release date postponed to September 3rd
  • Benchmark results
    • Discussion about the importance of I/O threading and vertical vs horizontal scaling
• Access to NPM @valkey namespace.
  • Apparently, it has been claimed by someone. We'll ask if it can be transferred to us, so we can use it for official Valkey NodeJS projects
• Upcoming conferences

Core team sync 2024-08-19

• Next Releases - 7.0.7 - Scoping fixes
• Valkey 8.0.0-rc2
  • Release date? (27th, GA on 16th).
    • All bug fixes on 26th. No more features after that.
  • Review pending items
    • All items having owners to close those week for rc2.
• Review Bloom RFC - https://github.com/valkey-io/valkey-rfc/pull/4
  • status
    • Directionally approved. Wait an additional week on feedback about compatibility and migration.

Core team sync 2024-08-12

• Roadmap for valkey + go - https://docs.google.com/document/d/1Tk7h58jLM-Pq4Tf8hqtQoW1vHI_-GY1TlKv7limwON8/edit#heading=h.xwi6nwrneyln
• Review JSON RFC - https://github.com/valkey-io/valkey-rfc/pull/2

Core team sync 2024-07-29

• Valkey 8 - We'll launch this week.
• Discuss the RFC process
  • Updates here: https://github.com/valkey-io/valkey-rfc/issues/5

Core team sync 2024-07-22

• Valkey 8-rc1
  • Fatlog - are we cutting this from rc1?
    • Yes
  • Per-slot statistics, PRs are close, just need a little bit more.
    • Discussed metrics, commented directly on PR.
  • Daily failure.
    • Reviewed failures and created issues for tracking. https://github.com/valkey-io/valkey/issues/858 https://github.com/valkey-io/valkey/issues/841
    • Main launch blocker was fixed related to slot stats underflow.
  • Launch date?
    • Try to hit this week?
  • Owner for other items such as release notes.
    • Ping is going to own release notes.
  • Supporting material like a blog post.
    • Ping will also take the pen on the notes.

Core team sync 2024-07-15

• Valkey 8-rc1
  • Launch date?
    • Sometime next week
  • Owner for other items such as release notes.
    • Ping volunteered
  • Supporting material like a blog post.
    • Madelyn is going to follow up with our developer advocates.
• Dual channel replication: https://github.com/valkey-io/valkey/pull/60
  • @Ping, what is pending?
    • Close on feature name: https://github.com/valkey-io/valkey/pull/60#issuecomment-2229078417
    • Update the PR description to use the official feature name: https://github.com/valkey-io/valkey/pull/60
• FSYNC always PR: Close and move PR to a different solution
• Cross version and fork compatibility testing: https://github.com/tair-opensource/resp-compatibility
  • Alibaba has some additional testing: https://github.com/tair-opensource/resp-compatibility
    • Does not cover upgrade testing. We will still need specific testing for that.

Core team sync 2024-07-08

• RDMA: https://github.com/valkey-io/valkey/pull/477
  • What is an experimental features
    • It is not built into the core by default
    • It is not subject to our API contracts (we can deprecate and or change it whenever)
    • We will decide at a later point if we want it to be a module vs as a core part of the engine.
  • Should we remove TLS build information from the documentation
    • Yes. We can also remove the testing information.
  • We should also move the TLS.md file to the README.md file.
    • @madolson will make an issue.
• How to handle official credentials/accounts for pypi, npm, etc. Storage for GPG private key (needed for Java). New clients: libvalkey-py, GLIDE
  • Folks will get access when they need it. @madelyn will give access to Viktor.
  • Merging libvalkey-py into the valkey organizations.
    • Followup with the requirements and validate it's needed. If it is, it should be gtg.
• Review topics on https://github.com/orgs/valkey-io/projects/2
  • Some issue: https://github.com/valkey-io/valkey/issues/547#issuecomment-2163406657