Joao Eduardo Luis

We should focus instead on having our documentation being built and provided through the website, which relies on docusaurus -- which should be able to do this fairly easily.

This will remain open, I believe this to be important to implement in the future (to be decided)

> IMO the `test_object_lock_delete_object_with_retention_and_marker` test is incorrect. I haven't read the test, but from your description I'm not so sure that's the case. AFAIU, the test is supposed to be...

Jesus and I have spoken about this. We first need to make sure issues are filed, and then we'll figure this out in the coming days. If you are aware...

> is it ok I take #592 ? (asking because not sure if anyone already working on this) Sounds good!

@0xavi0 feasible for v0.23.0? If not, we'll need to document this as unsupported for LH 1.6.

I think we can safely push this until after LH 1.6. We'll deal with this then, given its potentially annoying side-effects.

@giubacc last comment is based on the misconception that we no longer support them Helm chart. That is not the case. This issue is still relevant.

Agreed. I think this can go on the unsupported pile. This needs an entry in the compatibility matrix. If rgw itself does not support this, we should consider contributing this...

I have the feeling this is not necessarily a big problem when deploying in a container, so not a particular priority for LH 1.6 / v0.23.0. But we should still...