Skip to content

We need a policy to manage updates to impact services #11528

Description

@ptormene

This is related also to #11527.
It should be clear who is responsible for the decision to update the impact services, using which models and engine version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions