discuss: prepare release for v0.51.0

[Zheaoli]

Dear Apache OpenDAL community,

I will serve as the release manager for v0.51.0 and plan to release the first RC version before November 26th.
For this release, I would like to propose a special subtitle: "v0.51.0 - 本当の僕らをありがとう。" (Thank you for our true selves).

This phrase comes from "My Song", a touching piece from the anime "Angel Beats!". The song was performed by a character who, despite facing profound hardships, never lost her love for music and maintained her genuine appreciation for life.
By choosing this subtitle, I wish to bring cherished memories from the animation world into our own – to preserve a moment that reminds us of her unwavering spirit.

Please let me know if you have any questions about this version、

FYI:

1. My Song For Chind Mainland
2. My Song Youtube
3. Angel Beats!

Best

Manjusaka.

[Xuanwo]

Thank you @Zheaoli for working on this!

There is my +1 binding vote for the release title.

---

In this release, I want to include:

• Tracking issues of RFC-5313: Remove Metakey #5314
• Tracking issues of RFC-3911: Deleter API #3922

Both are breaking changes, which are better included simultaneously.

[Zheaoli]

Thanks for the vote

I will start the release process after #3922 and #5314

[Xuanwo]

I still have some great ideas to implement, but I believe it's better to save them for the next release. We can work on a release for now.

[simonsan]

Can you please consider including a version bump to suppaftp due to veeso/suppaftp#94 ?

Thank you! <3

[simonsan]

P.S.: You might even consider adding a deny.toml for cargo-deny and use this under bans:

[bans]
deny = [
  { crate = "aws-lc-rs", reason = "this crate introduces exorbitant build effort and breaks cross-compilation" },
  { crate = "aws-lc-sys", reason = "this crate introduces exorbitant build effort and breaks cross-compilation" },
]

So there is no possibility to pull in these crates via some version updates.

[Xuanwo]

Ideally, we don't need to increment suppaftp's patch version since users can freely update their Cargo.lock instead. However, I'm open to reviewing and merging a PR to update Cargo.toml for this change.