Document pmpu APIs as stabilised

[yonipeleg33]

Following up on #8103, and the subsequent discussion in #8108 - it appears that the pmpu APIs are already stable, but still tagged as "experimental".

The correct way to resolve this is by removing the experimental tag and documenting them properly (in docs/).
cc @talSofer

[N-o-Z]

@yonipeleg33, it's not experimental - the tag was left there and should have been removed earlier.
Can you please specify what stabilizing means? Is the API flaky? Do we have a bug? I think you might be using the wrong terminology

[yonipeleg33]

You're probably right, I meant only in the documentation level - removing the "experimental" tag, and adding proper documentation, following up on @arielshaqed's comment: #8108 (comment)

My intent with the original PR was fixing a technical "bug" in the documentation, but as it turned out, it is more big of a deal than I originally thought, so after discussing privately with @talSofer I decided to open a new issue for it and triage-ing it properly...

[yonipeleg33]

@N-o-Z I have updated the title and description, lmk if that's any better

[N-o-Z]

@N-o-Z I have updated the title and description, lmk if that's any better

Great! Thank you for clarifying

[Isan-Rivkin]

@N-o-Z why was this experimental in the first place? What changed since then? Is there full support for all Cloud vendors?
@arielshaqed - maybe you can shed more context on why was this experimental?

[arielshaqed]

@treeverse/product / @talSofer / @ozkatz happy for your input whether we should make it non-experimental.

AFAIK this works only for S3... but the "AF" in "AFAIK" is doing some heavy lifting, I don't know much.

[N-o-Z]

@N-o-Z why was this experimental in the first place? What changed since then? Is there full support for all Cloud vendors? @arielshaqed - maybe you can shed more context on why was this experimental?

This is one method of development we practice. We release something as experimental and if useful and works well we remove the experimental tag.
This was done a long time ago, and the decision to make it a "formal" API was taken a long time ago but was not executed.
This set of APIs is designed to work ONLY with S3. Enabling it for other block stores will require research into each storage we want to implement it for and might not be possible for some block stores