We achieved the project merging of Cactus and Weaver. We are preparing the initial repository including Cactus and Weaver codes.
We aim to bring as much Hyperledger interoperability work efforts together as possible to make the total output greater than the individual sums (code reuse enablement, shared testing infrastructure expertise, benchmarks, release management, etc.)
The plan is to leverage our mono-repo project structure in order to make the above plans as painless/as low overhead as possible since we want to actively prevent bogging down everybody involved with administrative changes/refactorings/breaking changes required in the name of collaboration
We continue to put effort into academic research (namely a research group within Hyperledger; several Hyperledger Summer Internships with a research component have been proposed and accepted).

Current Plans

The maintainers are planning the Cacti new architecture that is combined with the strengths of Cactus and Weaver. They will determine the Cacti v2 release plan and largely refactor the codes as the architecture.
They are also planning about some supporting tools such as ledger explorer interface of Cacti.
Currently there are some unstable behaviors of our CI scripts and our pull-requests are stopped to be merged, but we already made a counter measure and the problem will be fixed soon. => https://github.com/hyperledger/cactus/pull/2096
After the above problem are fixed, we plan to finish the security audit of the 1.0.0 release and issue patch releases as necessary based on the findings (1.0.1, 1.0.2 etc.)

Maintainer Diversity

As is required, you can find our current maintainer list here: https://github.com/hyperledger/cactus/blob/main/MAINTAINERS.md.