1. modules/sway:rollling quite unexpectedly had eol date in December. We are not ready to drop it yet, so I'm requesting to extend the eol date to a distant future.

I extended it to 2222-01-01

1. Despite being marked as eol for months, the module was branched into f34. That doesn't seem right to me, but from a brief look I haven't found any documentation or policy for modules EOL. Please, confirm if it's the expected behavior or redirect me to a right place for that question.

I guess it happened because of master stream in sway module: https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=sway&name=master&type=module

1. Would it be possible to untag the current sway:rollling module build from f34? I assume it's not too late do do this before beta freeze.
   That's a part of my long-term plan for removing unnecessary packages from the module and modularity owners already confirmed that no changes to the module package list are possible once it's shipped via stable release repositories.

We cannot untag the sway module that are already shipped out unless they are retired. You can build a new sway:rolling module by removing unnecessary packages and that will be what will be shipped in F34.

Thank you!

We cannot untag the sway module that are already shipped out unless they are retired. You can build a new sway:rolling module by removing unnecessary packages and that will be what will be shipped in F34.

As it was discussed previously[0], this solution is not possible/acceptable because it leaves previous releases stuck with non-updateable packages enforced via modular override dnf hack :-(.
Having separate modulemd definitions for f32-33 and f34-onwards would be the best solution for me, but I'm afraid that there's not only a policy limitation but also a technical one that forbids this.

[0] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HPQZO4GRFANHQRBW5VDRPRYG63KLAGQN/