ADR-36: Kernel repository separation

More details about this document
Latest published version:
GitHub decentraland/adr (pull requests, new issue, open issues)
Edit this documentation:
GitHub View commits View commits on

Context and Problem Statement

As of today, we already decoupled the renderer (decentraland/unity-renderer) from the explorer repository. And we are in the process of decoupling website (decentraland/explorer-website). The ECS and building tools are also in the path of being migrated to their own repositories (decentraland/js-sdk-toolchain).

The context of the problem is around the tactical/execution aspect. Since the changes affect directly the publishing cycles and processes of every package. We must optimize not blocking development and also not breaking things in a way that prevent us from releasing hotfixes.

Considered Options

Decision Outcome

We choose to create a separated repository to not block the releases and development of explorer during this migration stage.

Also having separated repositories, will foster external contributions, ensuring clear scopes and responsibilities for each repository.


Copyright and related rights waived via CC0-1.0. Living