Skip to content

Model the membership merges using TLA+ #407

@ktoso

Description

@ktoso

Would be nice to model the merge formally, to sanity check we're not missing any edge case.

The merges are generally simple, except for removal which involves some special handling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    1 - triagedTicket makes sense and is well defined, ready to be worked onhelp wantedGreat tickets to get started contributing!t:cluster:membership

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions